CODEWITHSUNDEEP
exceptioncassandrarepairnodetool
zhibo fu
zhibo fu

Reputation: 91

Cassandra 2.2.3 repair exception

I'm running a Cassandra cluster with version 2.2.3. The cluster consists of 3 nodes now, two of them are seeds and one is a normal node.

When I start repair on each node (command: nodetool repair -tr my_keyspace), I found the command was blocked on each node, I redirect the trace back information to the log and found there are many errors like the following:

Session completed with the following error: org.apache.cassandra.exceptions.RepairException: [repair #5717bb00-e685-11e5-801e-c71692f88562 on my_keyspace/node, (4856831381680181267,4878966233072304148]] Validation failed in /10.16.170.20

Has anyone faced the error before? Can we run Cassandra nodetool repair parallelly on each node?

Upvotes: 6

Views: 2085

Answers (2)

Zhong Hu
Zhong Hu

Reputation: 272

One guess is that when you run Cassandra repair, you'd better run repair node by node, which means only after one node is done, you start repair on the other node. The other thing is that on Cassandra 2.2 and above, incremental repair is the default and there're some discussion on using -pr together with incremental repair and the conclusion is not suggesting them used together(references:http://docs.datastax.com/en/archived/cassandra/2.2/cassandra/tools/toolsRepair.html and https://groups.google.com/forum/#!topic/nosql-databases/qzdbVLGFrD8) Hope these are helpful to you!

Upvotes: 1

zhibo fu
zhibo fu

Reputation: 91

I also found that if I execute nodetool repair without "-pr", the repair can complete successful more times, it seems that the "-pr" is not recommended after 2.2.x.:) Another I have found that execute nodetool repair without "-pr" parallelly on each node, it work good. However, there are no new data updated.

Upvotes: 1

Related Questions