[
https://issues.apache.org/jira/browse/CASSANDRA-6666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141239#comment-14141239
]
Donald Smith commented on CASSANDRA-6666:
-----------------------------------------
Perhaps this question is inappropriate here. But can tombstones be completely
omitted for system.hints, given that they're not replicated and given that only
internal code modifies them in normal operation? If a hint is delivered
successfully, why does it need a tombstone at all? If it times out, then
cassandra is going to give up on delivering it. So, again, why does it need a
tombstone? On the cassandra irc channel, several people speculated that
the cassandra developers didn't want to make a *special case* for system.hints.
Also, system.hints has *gc_grace_seconds=0*, so they won't survive a
compaction, presumably. I realize that in C* 3.0, tombstones will be moved out
of tables, but I still am perplexed why tombstones are needed at all for hints.
My apologies if this is a dumb question.
> 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
> Fix For: 2.0.11
>
> Attachments: 6666.txt, cassandra_system.log.debug.gz
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
