I had the same thing. Node restart should solve it. Shimi
On Sun, Apr 17, 2011 at 4:25 PM, Dikang Gu <dikan...@gmail.com> wrote: > +1. > > I also met this problem several days before, and I haven't got a solution > yet... > > > On Sun, Apr 17, 2011 at 9:17 PM, csharpplusproject < > csharpplusproj...@gmail.com> wrote: > >> Often, I see the following behavior: >> >> (1) Cassandra works, all nodes are up etc >> >> (2) a 'move' operation is being run on one of the nodes >> >> (3) following this 'move' operation, even after a couple of hours / days >> where it is obvious the operation has ended, the node which had 'moved' >> remains with a status of *?* >> >> perhaps it's a bug? >> >> >> ___________________________________________________________________________________ >> >> shalom@host:/opt/cassandra/apache-cassandra-0.7.4$ bin/nodetool -host >> 192.168.0.5 ring >> Address Status State Load Owns >> Token >> >> 127605887595351923798765477786913079296 >> 192.168.0.253 Up Normal 88.66 MB 25.00% >> 0 >> 192.168.0.4 Up Normal 558.2 MB 50.00% >> 85070591730234615865843651857942052863 >> 192.168.0.5 Up Normal 71.03 MB 16.67% >> 113427455640312821154458202477256070485 >> 192.168.0.6 Up Normal 44.71 MB 8.33% >> 127605887595351923798765477786913079296 >> >> shalom@host:/opt/cassandra/apache-cassandra-0.7.4$ bin/nodetool -host >> 192.168.0.4 move 92535295865117307932921825928971026432 >> >> shalom@host:/opt/cassandra/apache-cassandra-0.7.4$ bin/nodetool -host >> 192.168.0.5 ring >> Address Status State Load Owns >> Token >> >> 127605887595351923798765477786913079296 >> 192.168.0.253 Up Normal 171.17 MB 25.00% >> 0 >> 192.168.0.4 *?* Normal 212.11 MB 54.39% >> 92535295865117307932921825928971026432 >> 192.168.0.5 Up Normal 263.91 MB 12.28% >> 113427455640312821154458202477256070485 >> 192.168.0.6 Up Normal 26.21 MB 8.33% >> 127605887595351923798765477786913079296 >> > > > > -- > Dikang Gu > > 0086 - 18611140205 > >
