[ https://issues.apache.org/jira/browse/CASSANDRA-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860318#comment-13860318 ]
T Jake Luciani commented on CASSANDRA-6537: ------------------------------------------- My guess is we need to add the following to the autobootstrap case: {code} // if our schema hasn't matched yet, keep sleeping until it does // (post CASSANDRA-1391 we don't expect this to be necessary very often, but it doesn't hurt to be careful) while (!MigrationManager.isReadyForBootstrap()) { setMode(Mode.JOINING, "waiting for schema information to complete", true); try { Thread.sleep(1000); } catch (InterruptedException e) { throw new AssertionError(e); } } setMode(Mode.JOINING, "waiting for pending range calculation", true); PendingRangeCalculatorService.instance.blockUntilFinished(); setMode(Mode.JOINING, "calculation complete, ready to bootstrap", true); {code} > Starting node with auto_bootstrap false causes node to become replica for all > ranges > ------------------------------------------------------------------------------------ > > Key: CASSANDRA-6537 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6537 > Project: Cassandra > Issue Type: Bug > Reporter: T Jake Luciani > Assignee: Ryan McGuire > > We have a datacenter with 8 nodes and RF=3 > When trying to add a new node with auto_bootstrap false I noticed that > nodetool describering showed the new node was in the endpoint list for all > ranges. -- This message was sent by Atlassian JIRA (v6.1.5#6160)