1) yes 2) um, not sure. The nodetool output below looks like there are only 2 nodes in that cluster, i.e. there are no down nodes.
Aaron On 8/03/2011, at 2:11 PM, mcasandra wrote: > > aaron morton wrote: >> >> It's failing because when the node bootstraps it does not know about >> enough nodes to support the RF... >> >>> replication factor (3) exceeds number of >>> endpoints (2) >> >> I *think* the normal work around is to disable autobootstrap, bring the >> nodes up then run "nodetool join" or StorageService.joinRing() via the >> JConsole. >> >> I not tested this, but reading the code that looks OK. Can you try it out >> and let me know how it goes? >> >> Aaron >> > > I am getting confused about the behaviour: > > 1) Out of 3 nodes I have 2 nodes up and I am trying to start this node > that's failing. Is this expected that even though there are 2 nodes up one > node will continuously fail with "replication factor (3) exceeds .." > message? > > 2) When I brought 2 nodes down (out of 3), I was able to start one node > (with 66 % load below) even though auto_bootstrap is set to true. Shouldn't > it have failed for the same reason? > > $ nodetool -h `hostname` ring > Address Status State Load Owns Token > > 113427455640312821154458202477256070484 > 181.116.206.179 Up Normal 645.13 KB 33.33% 0 > 181.116.208.68 Up Normal 640.16 KB 66.67% > 113427455640312821154458202477256070484 > > > -- > View this message in context: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Exception-when-bringing-up-nodes-during-failure-testing-tp6085692p6099765.html > Sent from the cassandra-u...@incubator.apache.org mailing list archive at > Nabble.com.
