cassandra-commits mailing list archives

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

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

Sylvain Lebresne commented on CASSANDRA-6434:
---------------------------------------------

I'm confused. That ticket description sounds like it's about lowering the lifetime of tombstones
in the system but you make it sounds like it's not about that anymore. If this doesn't allow
to lower gc_grace, then why do we need that extra safety? Is it just really only extra safety
(to be clear, I'm really not a fan of the changes to LivenessInfo and DeletionTime and I'd
like to see if we can avoid it, but before that I need to understand why we're doing this
ticket in the first place).

> 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