[
https://issues.apache.org/jira/browse/CASSANDRA-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-5411.
---------------------------------------
Resolution: Won't Fix
I can't think of a better solution than "deliver or truncate your hints if you
need to modify gc_grace and don't want resurrection" either.
> Unexpired hints can potentially create previously deleted rows
> --------------------------------------------------------------
>
> Key: CASSANDRA-5411
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5411
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.10
> Environment: Ubuntu 10.04
> Reporter: Arya Goudarzi
> Priority: Minor
>
> Per discussion here:
> http://www.mail-archive.com/[email protected]/msg28905.html
> Hints are TTLed to lowest gc_grace_seconds. If we have hints that are not
> replayed, and the administrator updates schema to have lower gc_grace seconds
> on some CF, chances are compactions will delete tombstones and history of
> delete gets lost. If the deleted row is in some hints CF, since the TTL is
> not updated, chances are it gets replayed and the deleted row comes back to
> life.
> I think it would be nice as part of schema migration, to also update the TTLs
> on hints that already exists on any nodes hints column family.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
