Yes, I am running repairs in one single command.
Thanks Paulo!

Robert Sicoie

On Thu, Jan 5, 2017 at 1:59 PM, Paulo Motta <pauloricard...@gmail.com>
wrote:

> Fixed on https://issues.apache.org/jira/browse/CASSANDRA-12905 (still to
> be released). If you're running repair of all keyspace or tables in a
> single command, run each table separately and should improve things a bit.
>
> 2017-01-05 7:54 GMT-02:00 Robert Sicoie <robert.sic...@gmail.com>:
>
>> Hi guys,
>>
>> While running repairs, I see this on one box:
>>
>>
>> *ERROR [RepairJobTask:19] 2017-01-05 09:12:36,940 RepairSession.java:290
>> - [repair #3747c581-d325-11e6-92ea-130d59760dad] Session completed with the
>> following error*
>>
>> *org.apache.cassandra.exceptions.RepairException: [repair
>> #3747c581-d325-11e6-92ea-130d59760dad ...*
>>
>> *... Sync failed between /x.y.z.t and /x.y.z.v*
>> * at org.apache.cassandra.repair.Re
>> <http://org.apache.cassandra.repair.Re>moteSyncTask.syncComplete(RemoteSyncTask.java:67)
>> ~[apache-c*
>> *assandra-3.0.5.jar:3.0.5]*
>> * at org.apache.cassandra.repair.Re
>> <http://org.apache.cassandra.repair.Re>pairSession.syncComplete(RepairSession.java:211)
>> ~[apache-ca*
>> *ssandra-3.0.5.jar:3.0.5]*
>> * at
>> org.apache.cassandra.service.ActiveRepairService.handleMessage(ActiveRepairService.java:41*
>> *3) ~[apache-cassandra-3.0.5.jar:3.0.5]*
>> * at org.apache.cassandra.repair.Re
>> <http://org.apache.cassandra.repair.Re>pairMessageVerbHandler.doVerb(RepairMessageVerbHandler.java:*
>> *168) ~[apache-cassandra-3.0.5.jar:3.0.5]*
>> * at org.apache.cassandra.net
>> <http://org.apache.cassandra.net>.MessageDeliveryTask.run(MessageDeliveryTask.java:67)
>> ~[apache-cas*
>> *sandra-3.0.5.jar:3.0.5]*
>> * at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>> ~[na:1.8.0_60]*
>> * at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>> ~[na:1.8.0_60]*
>> * at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>> [na:1.8.0_*
>> *60]*
>> * at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> [na:1.8.0_*
>> *60]*
>> * at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]*
>>
>> And on /x.y.z.v I see this:
>>
>> *ERROR [StreamReceiveTask:27] 2017-01-05 09:12:36,892
>> StreamSession.java:520 - [Stream #b53eab60-d326-11e6-bbd3-d3d6e3ebef5c]
>> Streaming error occurred*
>> *org.apache.cassandra.exceptions.WriteTimeoutException: Operation timed
>> out - received only 0 responses.*
>> * at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:431)
>> ~[apache-cassandra-3.0.5.jar:3.0.5]*
>> * at org.apache.cassandra.db.Keyspace.lambda$apply$62(Keyspace.java:443)
>> ~[apache-cassandra-3.0.5.jar:3.0.5]*
>> * at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>> ~[na:1.8.0_60]*
>> * at
>> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:164)
>> ~[apache-cassandra-3.0.5.jar:3.0.5]*
>> * at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105)
>> ~[apache-cassandra-3.0.5.jar:3.0.5]*
>> * at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]*
>>
>>
>> Cassandra 3.0.5, 5 nodes, NetworkTopologyStrategy, single dc, RF=3
>>
>> This happened only recently a few times on several different boxes.
>>
>> How worried should I be?
>>
>> Thanks,
>> Robert
>>
>
>

Reply via email to