[
https://issues.apache.org/jira/browse/CASSANDRA-15854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-15854:
----------------------------------------
Fix Version/s: (was: 4.0-beta)
4.0-beta3
Since Version: 4.0-alpha1
Source Control Link:
https://github.com/apache/cassandra/commit/d4eba9faa1b57fed205813a639fe53bbbdc06ef1
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
committed with a small change - moved the parent repair session check to
{{RepairJob#executeTask}}, test run
[here|https://app.circleci.com/pipelines/github/krummas/cassandra/543/workflows/555d874f-8c47-41b0-bf95-80aeb9a75188]
(dtest failure is tracked in CASSANDRA-16094, looks unrelated to this), thanks
> Truncation should fail any ongoing repairs
> ------------------------------------------
>
> Key: CASSANDRA-15854
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15854
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Normal
> Fix For: 4.0-beta3
>
>
> Truncation may race with ongoing repairs, making it possible to clear data on
> one node but then stream data its truncation would have deleted from another
> node. We should abort any ongoing preview repairs if we get a truncation
> request.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
