[
https://issues.apache.org/jira/browse/CASSANDRA-19182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-19182:
--------------------------------------
Fix Version/s: 4.0.13
4.1.5
5.0-beta2
(was: 5.x)
(was: 4.0.x)
(was: 4.1.x)
(was: 5.0.x)
Since Version: 4.0
Source Control Link:
https://github.com/apache/cassandra/commit/c14abb40b2d0e2e1db121eac65a1264a287bcd18
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> IR may leak SSTables with pending repair when coming from streaming
> -------------------------------------------------------------------
>
> Key: CASSANDRA-19182
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19182
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: 4.0.13, 4.1.5, 5.0-beta2
>
> Attachments:
> ci_summary-trunk-a1010f4101bf259de3f31077540e4f987d5df9c5.html
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> There is a race condition where SSTables from streaming may race with pending
> repair cleanup in compaction causing us to cleanup the pending repair state
> in compaction while the SSTables are being added to it; this leads to IR
> failing in the future when those files get selected for repair.
> This problem was hard to track down as the in-memory state was wiped, so we
> don’t have any details. To better aid these types of investigation we should
> make sure the repair vtables get updated when IR session failures are
> submitted
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
