cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11696) Incremental repairs can mark too many ranges as repaired
Date Mon, 30 May 2016 13:59:13 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-11696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306691#comment-15306691
] 

Marcus Eriksson commented on CASSANDRA-11696:
---------------------------------------------

figured I should post a progress report on this as it is critical

Difficult part is handling snapshot repairs in 2.2+ since when we do repairs without anticompaction
we take a new snapshot for every range repaired. With this we need to take a single snapshot
when we start and reuse that over the repair session. Hoping to have a patch for review tomorrow.

> 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
>
> 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)

Mime
View raw message