; > From: wz1...@yahoo.com
> > Subject: Re: nodetool repair hung?
> > To: user@cassandra.apache.org
> >
> > check nodetool tpstats and looking for AntiEntropySessions/AntiEntropyStages
> > grep the log and looking for "repair" and "merkle
Thank you. It helped me.
> Date: Mon, 25 Mar 2013 15:22:32 -0700
> From: wz1...@yahoo.com
> Subject: Re: nodetool repair hung?
> To: user@cassandra.apache.org
>
> check nodetool tpstats and looking for AntiEntropySessions/AntiEntropyStages
> grep the log and looking for &quo
check nodetool tpstats and looking for AntiEntropySessions/AntiEntropyStages
grep the log and looking for "repair" and "merkle tree"
- Original Message -
From: "S C"
To: user@cassandra.apache.org
Sent: Monday, March 25, 2013 2:55:30 PM
Subject: node
I am using Cassandra 1.1.5.
nodetool repair is not coming back on the command line. Did it ran
successfully? Did it hang? How do you find if the repair was successful?I did
not find anything in the logs."nodetool compactionstats" and "nodetool
netstats" are clean.
nodetool compactionstats pend
I suspect you are in the case of
https://issues.apache.org/jira/browse/CASSANDRA-2290.
That is some neighbor node died or was unable to perform its part of the
repair. You can always
retry making sure all node are and stay alive to see if it is the former
one. But seeing the
other exception in you
On 08/03/2011 16:34, Sylvain Lebresne wrote:
I just saw repair hang here too, it's actually very easy to reproduce.
I'm looking at it right now.
--
Thanks. Should i bump GCGraceSeconds since i can no longer repair?
I tried repair on 3 nodes of a 6 node cluster and they all hang.
Woul
I just saw repair hang here too, it's actually very easy to reproduce. I'm
looking at it right now.
--
Sylvain
On Tue, Mar 8, 2011 at 4:30 PM, Karl Hiramoto wrote:
> I never saw this before upgrading to 0.7.3 but now I do nodetool repair and
> it sits there for hours. Previously it took about
I never saw this before upgrading to 0.7.3 but now I do nodetool repair
and it sits there for hours. Previously it took about 20 minutes per
node (about 10GB of data per node).
I had some OOM crashes, but haven't seen them since I increased the heap
size and decreased the key cache.
In the
