cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremiah Jordan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6434) Repair-aware gc grace period
Date Wed, 08 Jul 2015 14:31:05 GMT

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

Jeremiah Jordan commented on CASSANDRA-6434:
--------------------------------------------

It lets you reduce GC grace, not remove it completely.  So it doesn't need to be 7 days anymore,
but does need to be longer than the hint window and some other things.  So maybe we can reduce
it to a couple hours, or one day or something, and let the "don't drop un-repiared" make sure
we never drop one too early.
This also solves a "safety" issue.  If something happens to your cluster such that you can't
repair it in gc_grace, you aren't screwed, which is something people have to worry about now.

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

Mime
View raw message