[
https://issues.apache.org/jira/browse/CASSANDRA-11720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994168#comment-15994168
]
mck commented on CASSANDRA-11720:
---------------------------------
[~hnishi], my patch is updated with your modified description. that patch is
now at
https://github.com/michaelsembwever/cassandra/commit/f2344741a560c44538e88fb02cffa87f74445c9d
And the dtest patch is here –
https://github.com/michaelsembwever/cassandra-dtest/commit/f5267617cb23b8faa968ca2a11ccf49d0725a81d
> 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
> Assignee: Hiroyuki Nishi
> Priority: Minor
> Labels: lhf
> Fix For: 4.x
>
> 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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
