Bringing together the Apache Cassandra experts from the community and DataStax.

Want to learn? Have a question? Want to share your expertise? You are in the right place!

Not sure where to begin? Getting Started

 

question

LSpark avatar image
LSpark asked Erick Ramirez answered

OpsCenter reports "Cannot run anti-entropy repair on tables with NodeSync enabled"

Hi, I'm monitoring a DSE cluster and I see the following problem:

immagine-2022-03-23-181655.png

As you can see it says that the Repair is currently failing, this value keeps going up with time. Can someone explain to me what's happening in here? In the Opscenter logs I can only find this error:

microsoftteams-image-4.png

Is this related to the problem?


Checked logs and documentation.

opscenterrepairnodesync
10 |1000

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

steve.lacerda avatar image
steve.lacerda answered

From the image, it looks like you're trying to repair a table that already has nodesync enabled on the table. You can check the table schema for nodesync_enabled: true using cqlsh:

desc <keyspace>.<table>

In the properties, do you see nodesync_enabled: true? If so, you cannot repair that table, and you'll need to either need to disable nodesync on that table:

https://docs.datastax.com/en/dse/6.7/dse-dev/datastax_enterprise/tools/dseNodesync/dseNodesyncEnable.html

Or disable repairs on the table:

https://docs.datastax.com/en/opscenter/6.8/opsc/online_help/services/excludeKStablesSubR.html

Share
10 |1000

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

Erick Ramirez avatar image
Erick Ramirez answered

It looks like you've asked the same question on Stack Overflow so I'm re-posting my answer here.


NodeSync is a new feature in DataStax Enterprise which runs a repair continuously in the background using the same mechanism as read-repairs and replaces the traditional anti-entropy repairs.

The OpsCenter Repair Service will skip repairs on tables which have NodeSync enabled because it isn't possible to run traditional repairs on them as I've explained in question #3879.

If NodeSync was enabled on a table while a repair on that same table was already scheduled and running, it would explain why you're seeing error messages.

You can stop the errors from being generated by explicitly excluding the keyspace(s) or table(s) from subrange repairs with:

[repair_service]
ignore_keyspaces=ks_name_1,ks_name_2
ignore_tables=ks_name_3.table_name_1,ks_name_3.table_name_2
Share
10 |1000

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.