[
https://issues.apache.org/jira/browse/CASSANDRA-11696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15342369#comment-15342369
]
Joel Knighton commented on CASSANDRA-11696:
-------------------------------------------
I've rebased the branches and run dtests for
[2.1|http://cassci.datastax.com/view/Dev/view/jkni/job/jkni-11696-2.1-dtest/],
[2.2|http://cassci.datastax.com/view/Dev/view/jkni/job/jkni-11696-2.2-dtest/],
[3.0|http://cassci.datastax.com/view/Dev/view/jkni/job/jkni-11696-3.0-dtest/],
and
[trunk|http://cassci.datastax.com/view/Dev/view/jkni/job/jkni-11696-trunk-dtest/].
They all look clean relative to upstream, so all that remains is the few nits
above.
> Incremental repairs can mark too many ranges as repaired
> --------------------------------------------------------
>
> Key: CASSANDRA-11696
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11696
> Project: Cassandra
> Issue Type: Bug
> Reporter: Joel Knighton
> Assignee: Marcus Eriksson
> Priority: Critical
> Fix For: 2.1.x, 2.2.x, 3.0.x, 3.x
>
>
> Incremental repairs are tracked using a parent session - a subordinate repair
> session is created for each range in the repair. When a node participating in
> the repair receives a validation request, it will reference the sstables in
> the parent repair session. When all subordinate sessions conclude, each node
> anticompacts SSTables based on the parent repair session for the whole range
> of the repair, but these referenced SSTables may have only been present for
> the validation of some subset of the ranges because the SSTables were created
> concurrent with the parent repair session.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
