[
https://issues.apache.org/jira/browse/CASSANDRA-20996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaydeepkumar Chovatia updated CASSANDRA-20996:
----------------------------------------------
Epic Link: CASSANDRA-19918
> Auto-repair scheduler should use LWTs for all auto-repair history operations
> ----------------------------------------------------------------------------
>
> Key: CASSANDRA-20996
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20996
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Consistency/Repair
> Reporter: Kristijonas Zalys
> Assignee: Kristijonas Zalys
> Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The auto-repair scheduler seems to use LWTs only for a subset of the
> mutations on auto-repair history. This has lead to situations where we have
> one node trying to delete an entry from the auto-repair history and another
> node trying modify this entry at the same time. In the end, we end up with a
> corrupted entry in the auto-repair history.
> We should fix this by making the auto-repair scheduler use LWTs for all
> auto-repair system table mutations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
