On 11/01/2013 03:03 PM, Robert Coli wrote:
On Fri, Nov 1, 2013 at 9:36 AM, Narendra Sharma
wrote:
I was successfully able to bootstrap the node. The issue was RF > 2.
Thanks again Robert.
For the record, I'm not entirely clear why bootstrapping two nodes into the
same range should have cause
On Fri, Nov 1, 2013 at 9:36 AM, Narendra Sharma
wrote:
> I was successfully able to bootstrap the node. The issue was RF > 2.
> Thanks again Robert.
>
For the record, I'm not entirely clear why bootstrapping two nodes into the
same range should have caused your specific bootstrap problem, but I a
I was successfully able to bootstrap the node. The issue was RF > 2. Thanks
again Robert.
On Wed, Oct 30, 2013 at 10:29 AM, Narendra Sharma wrote:
> Thanks Robert.
>
> I didn't realize that some of the keyspaces (not all and esp. the biggest
> one I was focusing on) had RF > 2. I wasted 3 days
Thanks Robert.
I didn't realize that some of the keyspaces (not all and esp. the biggest
one I was focusing on) had RF > 2. I wasted 3 days on it. Thanks again for
the pointers. I will try again and share the results.
On Wed, Oct 30, 2013 at 12:28 AM, Robert Coli wrote:
> On Tue, Oct 29, 2013
On Tue, Oct 29, 2013 at 11:45 AM, Narendra Sharma wrote:
> We had a cluster of 4 nodes in AWS. The average load on each node was
> approx 750GB. We added 4 new nodes. It is now more than 30 hours and the
> node is still in JOINING mode.
> Specifically I am analyzing the one with IP 10.3.1.29. The
