cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (Jira)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-14309) Make hint window persistent across restarts
Date Fri, 27 Aug 2021 13:45:00 GMT

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

Brandon Williams commented on CASSANDRA-14309:
----------------------------------------------

bq. the decision whether a node should receive a hint in case a node for which topology changed
happened to receive it should not take into account if there is or is not some earlier hint
for that node from the perspective of the node which received that hint which is not meant
to be for it.

I think in this case we should not do the check and just store the hint.  It's better to err
on the side of possibly more hints than maintaining perfect accuracy of the hint window, and
this scenario won't be super common.

> Make hint window persistent across restarts
> -------------------------------------------
>
>                 Key: CASSANDRA-14309
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14309
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Consistency/Hints
>            Reporter: Kurt Greaves
>            Assignee: Stefan Miklosovic
>            Priority: Low
>             Fix For: 4.1
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> The current hint system stores a window of hints as defined by {{max_hint_window_in_ms}},
however this window is not persistent across restarts.
> Examples (cluster with RF=3 and 3 nodes, A, B, and C):
>  # A goes down
>  # X ms of hints are stored for A on B and C
>  # A is restarted
>  # A goes down again without hints replaying from B and C
>  # B and C will store up to another {{max_hint_window_in_ms}} of hints for A
>  
>  # A goes down
>  # X ms of hints are stored for A on B and C
>  # B is restarted
>  # B will store up to another {{max_hint_window_in_ms}} of hints for A
>  
> Note that in both these scenarios they can continue forever. If A or B keeps getting
restarted hints will continue to pile up.
>  
> Idea of this ticket is to stop this behaviour from happening and only ever store up to
{{max_hint_window_in_ms}} of hints for a particular node.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message