Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 10 Aug 2015 14:48:49 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12682243.1386023398000.21932.1439218129720@Atlassian.JIRA>
In-Reply-To: <JIRA.12682243.1386023398000@Atlassian.JIRA>
References: <JIRA.12682243.1386023398000@Atlassian.JIRA>
 <JIRA.12682243.1386023398421@arcas>
Subject: [jira] [Comment Edited] (CASSANDRA-6434) Repair-aware gc grace
 period
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis edited comment on CASSANDRA-6434 at 8/10/15 2:48 PM:
--------------------------------------------------------------------

Sylvain is out for another week. Can you review [~kohlisankalp]?

Edit: turns out Yuki is already working on it, assigning to him.


was (Author: jbellis):
Sylvain is out for another week. Can you review [~kohlisankalp]?

> Repair-aware gc grace period 
> -----------------------------
>
>                 Key: CASSANDRA-6434
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6434
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: sankalp kohli
>            Assignee: Marcus Eriksson
>             Fix For: 3.0 beta 1
>
>
> Since the reason for gcgs is to ensure that we don't purge tombstones until every replica has been notified, it's redundant in a world where we're tracking repair times per sstable (and repairing frequentily), i.e., a world where we default to incremental repair a la CASSANDRA-5351.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)