cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sankalp kohli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5988) Make hint TTL customizable
Date Wed, 12 Oct 2016 04:13:20 GMT

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

sankalp kohli commented on CASSANDRA-5988:
------------------------------------------

[~iamaleksey] I could not search "cassandra.maxHintTTL" in 3.0.9. With new hints in 3.0, how
can we change this?

> Make hint TTL customizable
> --------------------------
>
>                 Key: CASSANDRA-5988
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5988
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Oleg Kibirev
>            Assignee: Vishy Kasar
>              Labels: patch
>             Fix For: 1.2.12, 2.0.3
>
>         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.3.4#6332)

Mime
View raw message