Aleksey Yeschenko commented on CASSANDRA-5988:

[~kohlisankalp] Will need to either modify {{HintsDispatcher}} logic to take 
'maxhintttl' into account (compared to current time - hint's creationTime), or 
do the same even earlier, in {{HintsReader}}. The former is probably cleaner; 
the latter can be done a bit more efficiently - skipping hint body entirely if 
gcgs/creationTime/maxhinttl combination says the hint is basically dead.

Don't have time atm to do it, but [~bdeggleston] should be pretty familiar with 
that code, as he added compression logic - I can review.

> 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

Reply via email to