org.apache.cassandra.exceptions.RepairException

[repair #bb979050-bad9-11e5-90e5-edb5e4de409d on our_keyspace/table_one, (-3542169710435610193,-2435099955373091584]] Sync failed between /62.xx.xx.xx and /52.xx.xx.xx

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web26

  • [repair #bb979050-bad9-11e5-90e5-edb5e4de409d on our_keyspace/table_one, (-3542169710435610193,-2435099955373091584]] Sync failed between /62.xx.xx.xx and /52.xx.xx.xx
  • via serverfault.com by Unknown author, 1 year ago
    [repair #bb979050-bad9-11e5-90e5-edb5e4de409d on our_keyspace/table_one, (-3542169710435610193,-2435099955373091584]] Sync failed between /62.xx.xx.xx and /52.xx.xx.xx
  • via Google Groups by Jean Carlo, 11 months ago
    [repair #41e4bab0-5a63-11e6-9993-e11d93fd5b40 on ks/cf_adv, (487410372471205090,492009442088088379]] Sync failed between /192.168.0.144 and /192.168.0.37
  • Stack trace

    • org.apache.cassandra.exceptions.RepairException: [repair #bb979050-bad9-11e5-90e5-edb5e4de409d on our_keyspace/table_one, (-3542169710435610193,-2435099955373091584]] Sync failed between /62.xx.xx.xx and /52.xx.xx.xx at org.apache.cassandra.repair.RemoteSyncTask.syncComplete(RemoteSyncTask.java:67)[apache-cassandra-2.2.4.jar:2.2.4] at org.apache.cassandra.repair.RepairSession.syncComplete(RepairSession.java:211)[apache-cassandra-2.2.4.jar:2.2.4] at org.apache.cassandra.service.ActiveRepairService.handleMessage(ActiveRepairService.java:415)[apache-cassandra-2.2.4.jar:2.2.4] at org.apache.cassandra.repair.RepairMessageVerbHandler.doVerb(RepairMessageVerbHandler.java:163)[apache-cassandra-2.2.4.jar:2.2.4] at org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:67)[apache-cassandra-2.2.4.jar:2.2.4] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[na:1.8.0_65] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[na:1.8.0_65] at java.lang.Thread.run(Thread.java:745)[na:1.8.0_65]

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.