[
https://issues.apache.org/jira/browse/CASSANDRA-11720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15992489#comment-15992489
]
Romain Hardouin commented on CASSANDRA-11720:
---------------------------------------------
It would be nice to have that in nodetool. I use jmxterm to do that currently:
{code}
echo "set -b org.apache.cassandra.db:type=StorageProxy MaxHintWindow <value>" |
java -jar /path/to/jmxterm.jar -l 127.0.0.1:7199 -u ... -p ...
{code}
Some comments:
In {{SetMaxHintWindow}} it should be {{value_in_ms}}:
{code}
usage = "<value_in_mb>"
{code}
In {{GetMaxHintWindow}} I don't understand "of the given type" here:
{code}
@Command(name = "getmaxhintwindow", description = "Print the max hint window of
the given type in ms")
{code}
Maybe just {{Print max hint window in ms}}?
Thanks
> 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
