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

["Hiroyuki Nishi (JIRA)" <ji...@apache.org>]

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

Hiroyuki Nishi commented on CASSANDRA-11720:
--------------------------------------------

Hello,

I fixed this issue. Below is a sample result.

{code}
$ ./bin/nodetool getmaxhintwindow
Current max hint window: 10800000 ms

$ ./bin/nodetool setmaxhintwindow 0

$ ./bin/nodetool getmaxhintwindow  
Current max hint window: 0 ms
{code}

Could someone review the attached patch?
I worked in trunk branch.

Thank you.

> 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)