cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiroyuki Nishi (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11720) Changing `max_hint_window_in_ms` at runtime
Date Wed, 03 May 2017 01:43:04 GMT


Hiroyuki Nishi commented on CASSANDRA-11720:

I'm sorry that you are confused in my English.

Thank you for updating the patch.
I would like to modify the description of setmaxhintwindow additionally as follows.

Please let me know what you think.

> Changing `max_hint_window_in_ms` at runtime
> -------------------------------------------
>                 Key: CASSANDRA-11720
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message