You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2015/08/10 16:48:49 UTC
[jira] [Comment Edited] (CASSANDRA-6434) Repair-aware gc grace
period
[ 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)