[
https://issues.apache.org/jira/browse/CASSANDRA-19182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17814476#comment-17814476
]
David Capwell commented on CASSANDRA-19182:
-------------------------------------------
[~e.dimitrova] issues with CI... since this goes back to 4.0 we need our CI
working correctly and it has been having issues with 4.0... so merging this got
put on hold until thats fixed =(
> 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.x, 4.1.x, 5.0.x, 5.x
>
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
