if the boxes are idle, you could use jstack and look at the stack… perhaps it's locked somewhere.
Worth a shot. On Tue, Jul 1, 2014 at 9:24 AM, Brian Tarbox <tar...@cabotresearch.com> wrote: > I have a six node cluster in AWS (repl:3) and recently noticed that repair > was hanging. I've run with the "-pr" switch. > > I see this output in the nodetool command line (and also in that node's > system.log): > Starting repair command #9, repairing 256 ranges for keyspace dev_a > > but then no other output. And I see nothing in any of the other node's > log files. > > Right now the application using C* is turned off so there is zero activity. > I've let it be in this state for up to 24 hours with nothing more logged. > > Any suggestions? > -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts> <http://spinn3r.com>
