Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 1 Feb 2017 22:54:52 +0000 (UTC)
From: "Marcus Eriksson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12819508.1428538488000.11681.1485989692376@Atlassian.JIRA>
In-Reply-To: <JIRA.12819508.1428538488000@Atlassian.JIRA>
References: <JIRA.12819508.1428538488000@Atlassian.JIRA> <JIRA.12819508.1428538488067@jira-lw-us.apache.org>
Subject: [jira] [Updated] (CASSANDRA-9143) Improving consistency of repairAt
 field across replicas
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 01 Feb 2017 22:55:00 -0000


     [ https://issues.apache.org/jira/browse/CASSANDRA-9143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Eriksson updated CASSANDRA-9143:
---------------------------------------
    Fix Version/s: 4.0

> Improving consistency of repairAt field across replicas 
> --------------------------------------------------------
>
>                 Key: CASSANDRA-9143
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9143
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: sankalp kohli
>            Assignee: Blake Eggleston
>             Fix For: 4.x
>
>
> We currently send an anticompaction request to all replicas. During this, a node will split stables and mark the appropriate ones repaired. 
> The problem is that this could fail on some replicas due to many reasons leading to problems in the next repair. 
> This is what I am suggesting to improve it. 
> 1) Send anticompaction request to all replicas. This can be done at session level. 
> 2) During anticompaction, stables are split but not marked repaired. 
> 3) When we get positive ack from all replicas, coordinator will send another message called markRepaired. 
> 4) On getting this message, replicas will mark the appropriate stables as repaired. 
> This will reduce the window of failure. We can also think of "hinting" markRepaired message if required. 
> Also the stables which are streaming can be marked as repaired like it is done now. 


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)