> > nodetool repair is not coming back on the command line As a side, nodetool command makes a call to the server for each KS you are repairing. The calls are done in serial and if your terminal session times out the repair will stop after the last call nodetool made.
If I'm manually running nodetool I run it in a screen . Cheers ----------------- Aaron Morton Freelance Cassandra Consultant New Zealand @aaronmorton http://www.thelastpickle.com On 26/03/2013, at 4:00 PM, S C <as...@outlook.com> wrote: > 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 "repair" and "merkle tree" > > > > ----- Original Message ----- > > From: "S C" <as...@outlook.com> > > To: user@cassandra.apache.org > > Sent: Monday, March 25, 2013 2:55:30 PM > > Subject: nodetool repair hung? > > > > > > 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 > > pending tasks: 0 > > Active compaction remaining time : n/a > > > > > > > > > > > > nodetool netstats > > Mode: NORMAL > > Not sending any streams. > > Not receiving any streams. > > Pool Name Active Pending Completed > > Commands n/a 0 121103621 > > Responses n/a 0 209564496 > > > > > > > > > > > >
