thanks for the help! On Sun, Aug 7, 2011 at 2:10 PM, Dikang Gu <dikan...@gmail.com> wrote:
> Yes, I think you are right. > > The "nodetool move" will move the keys on the node to the other two nodes, > and the required replication is 3, but you will only have 2 live nodes after > the move, so you have the exception. > > > On Sun, Aug 7, 2011 at 2:03 PM, Yan Chunlu <springri...@gmail.com> wrote: > >> is that possible that the implements of cassandra only calculate live >> nodes? >> >> for example: >> "node move node3" cause node3 "Leaving", then cassandra iterate over the >> endpoints and found node1 and node2. so the endpoints is 2, but RF=3, >> Exception raised. >> >> is that true? >> >> >> >> On Fri, Aug 5, 2011 at 3:20 PM, Yan Chunlu <springri...@gmail.com> wrote: >> >>> nothing... >>> >>> nodetool -h node3 netstats >>> Mode: Normal >>> Not sending any streams. >>> Nothing streaming from /10.28.53.11 >>> Pool Name Active Pending Completed >>> Commands n/a 0 186669475 >>> Responses n/a 0 117986130 >>> >>> >>> nodetool -h node3 compactionstats >>> compaction type: n/a >>> column family: n/a >>> bytes compacted: n/a >>> bytes total in progress: n/a >>> pending tasks: 0 >>> >>> >>> >>> On Fri, Aug 5, 2011 at 1:47 PM, mcasandra <mohitanch...@gmail.com> >>> wrote: >>> > Check things like netstats, disk space etc to see why it's in Leaving >>> state. >>> > Anything in the logs that shows Leaving? >>> > >>> > -- >>> > View this message in context: >>> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/move-one-node-for-load-re-balancing-then-it-status-stuck-at-Leaving-tp6655168p6655326.html >>> > Sent from the cassandra-u...@incubator.apache.org mailing list archive >>> at Nabble.com. >>> > >>> >> >> > > > -- > Dikang Gu > > 0086 - 18611140205 > >
