Hello Sebastien,

Not sure but have you checked the output of "nodetool describecluster"? A 
schema mismatch or node unavailability might result in this.


Thanks,

Dipan Shah

________________________________
From: Sébastien Rebecchi <srebec...@kameleoon.com>
Sent: Wednesday, May 26, 2021 7:35 PM
To: user@cassandra.apache.org <user@cassandra.apache.org>
Subject: unable to repair

Hi,

I have an issue with repairing my Casandra cluster, that was already the case 
with Cassandra 3 and the issue is not solved with Cassandra 4 RC1.

I run in a for loop, one 1 by 1, the following command:

nodetool -h THE_NODE -u jTHE_USER -pw THE_PASSWORD repair --full -pr

and I always get the following error, see message and stack trace for Cassandra 
4 RC1 at the bottom of the message (the same for C3).

I don't know what to do with that. Are there some mistakes I could have made in 
my table design explaining that? I have heard for example that it was not 
recommended to have big partitions, so I changed my data model to remove 
clustering keys I add before and then split big partitions in many independent 
one, and now the partitions are max 500KB each (the vast majority of them are 
max 100KB). But it did not change anything. Also my partition key was a 
compound of 9 columns and I changed that to have only 1 column for partition 
key by generating ids by myself, the same, no improvement.

Thank you for your help,

Sébastien

--

error: Repair job has failed with the error message: [2021-05-26 15:54:19,981] 
Repair command #2 failed with error Got negative replies from endpoints 
[135.181.222.100, 135.181.217.109, 135.181.221.180]
-- StackTrace --
java.lang.RuntimeException: Repair job has failed with the error message: 
[2021-05-26 15:54:19,981] Repair command #2 failed with error Got negative 
replies from endpoints [135.181.222.100, 135.181.217.109, 135.181.221.180]
at org.apache.cassandra.tools.RepairRunner.progress(RepairRunner.java:116)
at 
org.apache.cassandra.utils.progress.jmx.JMXNotificationProgressListener.handleNotification(JMXNotificationProgressListener.java:77)
at 
com.sun.jmx.remote.internal.ClientNotifForwarder$NotifFetcher.dispatchNotification(ClientNotifForwarder.java:583)
at 
com.sun.jmx.remote.internal.ClientNotifForwarder$NotifFetcher.doRun(ClientNotifForwarder.java:533)
at 
com.sun.jmx.remote.internal.ClientNotifForwarder$NotifFetcher.run(ClientNotifForwarder.java:452)
at 
com.sun.jmx.remote.internal.ClientNotifForwarder$LinearExecutor$1.run(ClientNotifForwarder.java:108)

Reply via email to