On Tue, Apr 24, 2012 at 3:24 PM, Bill Au wrote:
> Everything went smoothly until I ran the last step, which is to run nodetool
> repair on all the nodes in the new data center. Repair is hanging on all
> the new nodes. I had to hit control-C to break out of it.
> [ snip ]
> Did I missed anything
I just followed the step outlined in this email thread to add a second data
center to my existing cluster. I am running 1.0.8. Each data center has a
replication factor of 2. I am using local quorum for read and write.
Everything went smoothly until I ran the last step, which is to run
nodetool
Jeremiah,
Thanks!
I'm running 1.0.8, two interesting things to note:
- I don't have sufficient disk space to handle the straight bump to a
replication factor of 4, so I think I'm going to have to do it one by
one (1,2,3 and 4) with a bunch of cleanups in between.
- Also, using a LOCAL_QUORU
You need to make sure your clients are reading using LOCAL_* settings so
that they don't try to get data from the other data center. But you
shouldn't get errors while replication_factor is 0. Once you change the
replication factor to 4, you should get missing data if you are using
LOCAL_* fo
Everything that I've read about data centers focuses on setting things
up at the beginning of time.
I've the the following situation:
10 machines in a datacenter (DC1), with replication factor of 2.
I want to set up a second data center (DC2) with the following
configuration:
20 machines w