You should be able to tell from earlier in the log if this is from a
request, from hinted handoff replay, or something else
On Wed, Jul 20, 2011 at 10:42 PM, Yan Chunlu springri...@gmail.com wrote:
thans for the reply.
now the problem is how can I get rid of the N of 2147483647 , it seems
this time it is another node, the node goes down during repair, and come
back but never up, I change log level to DEBUG and found out it print out
the following message infinitely
DEBUG [main] 2011-07-20 20:58:16,286 SliceQueryFilter.java (line 123)
collecting 0 of 2147483647:
sorry for the misunderstanding. I saw many N of 2147483647 which N=0 and
thought it was not doing anything.
my node was very unbalanced and I was intend to rebalance it by nodetool
move after a node repair, does that cause the slices much large?
Address Status State Load
Personally I would do a repair first if you need to do one, just so you are
confident everything is where is should be.
Then do the move as described in the wiki.
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 21 Jul 2011, at
thans for the reply.
now the problem is how can I get rid of the N of 2147483647 , it seems
never ends, and the node never goes UP
last time it happens I run node cleanup, turns out some data loss(not sure
if caused by cleanup).
On Thu, Jul 21, 2011 at 11:37 AM, aaron morton
