Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow for configurable LWT CL #1542

Open
rustyrazorblade opened this issue Feb 13, 2025 · 0 comments
Open

Allow for configurable LWT CL #1542

rustyrazorblade opened this issue Feb 13, 2025 · 0 comments

Comments

@rustyrazorblade
Copy link
Contributor

rustyrazorblade commented Feb 13, 2025

First, for context, updating running repairs uses a SERIAL consistency level:

setRunningRepairsPrepStmt = session
        .prepare(
            "UPDATE running_repairs USING TTL ?"
                + " SET reaper_instance_host = ?, reaper_instance_id = ?, segment_id = ?"
                + " WHERE repair_id = ? AND node = ? IF reaper_instance_id = ?")
        .setSerialConsistencyLevel(ConsistencyLevel.SERIAL)
        .setConsistencyLevel(ConsistencyLevel.QUORUM)
        .setIdempotent(false);

In a deployment with multiple datacenters, this is used to ensure multiple reaper instances don't stomp all over each other. However, if you're running a single reaper out of 1 DC and using it to coordinate, it's unnecessary. Normally, I'd just recommend confining the reaper keyspace to a single DC to avoid the problem, but when using k8ssandra, it forces you to use a multi-dc setup and I'm finding LWTs are constantly timing out.

This issue to make Reaper configurable to be able to use ConsistenyLevel.LOCAL_SERIAL.

┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: REAP-199

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant