cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5988) Make hint TTL customizable
Date Thu, 12 Sep 2013 18:27:52 GMT


Jonathan Ellis commented on CASSANDRA-5988:

Hint TTL will be exactly gc grace for the reasons documented in CASSANDRA-5314.

"using backdated deletes as a form of optimistic locking" sounds like a bad idea, would you
care to defend it? :)
> Make hint TTL customizable
> --------------------------
>                 Key: CASSANDRA-5988
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Oleg Kibirev
> Currently time to live for stored hints is hardcoded to be gc_grace_seconds. This causes
problems for applications using backdated deletes as a form of optimistic locking. Hints for
updates made to the same data on which delete was attempted can persist for days, making it
impossible to determine if delete succeeded by doing read(ALL) after a reasonable delay. We
need a way to explicitly configure hint TTL, either through schema parameter or through a
yaml file.

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:

View raw message