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 15:09:05 GMT

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

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

bq. Could we just never drop a tombstone on the read path?

There is 2 (linked) reasons we drop purgeable tombstones on reads:
# it's a minor optimization: the sooner we get rid of stuff we don't need, the better.
# it makes sure we don't throw a TombstoneOverwhelming because of them (which *has* happened
in the wild and is not terribly nice because we want tombstone overwhelming exception to mean
"you've done something wrong while modeling" while purgeable tombstones are just an artifact
of compaction lagging behind, which could be temporary and not a huge deal).

> 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