You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "mck (JIRA)" <ji...@apache.org> on 2016/11/08 22:45:59 UTC

[jira] [Updated] (CASSANDRA-11720) Changing `max_hint_window_in_ms` at runtime

     [ https://issues.apache.org/jira/browse/CASSANDRA-11720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

mck updated CASSANDRA-11720:
----------------------------
    Reviewer: mck

> Changing `max_hint_window_in_ms` at runtime
> -------------------------------------------
>
>                 Key: CASSANDRA-11720
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11720
>             Project: Cassandra
>          Issue Type: Wish
>          Components: Coordination
>            Reporter: Jens Rantil
>            Priority: Minor
>              Labels: lhf
>         Attachments: CASSANDRA-11720-trunk.patch
>
>
> Scenario: A larger node (in terms of data it holds) goes down. You realize that it will take slightly more than `max_hint_window_in_ms` to fix it. You have a the disk space to store some additional hints.
> Proposal: Support changing `max_hint_window_in_ms` at runtime. The change doesn't have to be persisted somewhere. I'm thinking similar to changing the `compactionthroughput` etc. using `nodetool`.
> Workaround: Change the value in the configuration file and do a rolling restart of all the nodes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)