[
https://issues.apache.org/jira/browse/CASSANDRA-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams resolved CASSANDRA-5411.
-
Resolution: Won't Fix
Fix Version/s: (was: 1.2.4)
This isn't as simple as I originally thought, since hints store the original
serialized mutation, which can cross multiple CFs, causing us to have to see
which ones actually need to be removed, and then serialize the remainder in a
new mutation. This is getting expensive, so I'd rather just say "deliver or
truncate your hints if you need to modify gc_grace and don't want resurrection."
> 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
>Assignee: Brandon Williams
>
> Per discussion here:
> http://www.mail-archive.com/user@cassandra.apache.org/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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
