You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Vishy Kasar (JIRA)" <ji...@apache.org> on 2013/10/21 23:33:52 UTC

[jira] [Commented] (CASSANDRA-5988) Make hint TTL customizable

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

Vishy Kasar commented on CASSANDRA-5988:
----------------------------------------

Attached the diff as a file 5988.txt

> Make hint TTL customizable
> --------------------------
>
>                 Key: CASSANDRA-5988
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5988
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Oleg Kibirev
>              Labels: patch
>         Attachments: 5988.txt
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)