On Fri, Nov 28, 2014 at 6:46 AM, Reynald BOURTEMBOURG < reynald.bourtembo...@esrf.fr> wrote:
> We have a three nodes cluster running Cassandra 2.1.2 on Linux Debian 7. > More than 2 hours later, I executed "nodetool repair" on one of the nodes > (cass2). > It started to repair the keyspace we created (RF=3) and it got stuck there. > The nodetool repair command didn't return yet. > Yes, repair has historically not really worked, and still hangs sometimes. Search the archives for tons of posts where I link various JIRA tickets with background. On the plus side, so many people have had such a negative experience for so long that the squeaky wheel is finally getting the grease. Significant improvements have been made in the reliability and transparency of repair in recent versions. > Is there anything that you could suggest me to do before to restart any > node in order to try to better understand the origin of this problem, if > this is an unknown issue? > You could use the JMX endpoint to stop repair, but if you have vnodes it's probably easier to just restart the affected nodes. https://issues.apache.org/jira/browse/CASSANDRA-3486 =Rob
