cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Smith (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6666) Avoid accumulating tombstones after partial hint replay
Date Sun, 28 Sep 2014 15:33:35 GMT

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

Donald Smith commented on CASSANDRA-6666:
-----------------------------------------

I know this is moot because of the redesign of hints, but I want to understand this. OK, if
a hint was successfully delivered, then I can see how a tombstone would be useful for causing
deletion of *older* instances in other sstables.  But if a hint timed-out (tombstone), then
any older instance will also have timed out (presumably). So, could tombstones be deleted
in that case (timeout)?  Perhaps a timed out cell IS a tombstone, but my point is: I don't
see why they need to take up space.

> Avoid accumulating tombstones after partial hint replay
> -------------------------------------------------------
>
>                 Key: CASSANDRA-6666
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6666
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>              Labels: hintedhandoff
>         Attachments: 6666.txt, cassandra_system.log.debug.gz
>
>




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

Mime
View raw message