cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mck (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-11720) Changing `max_hint_window_in_ms` at runtime
Date Wed, 10 May 2017 04:28:04 GMT

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

mck updated CASSANDRA-11720:
----------------------------
    Fix Version/s:     (was: 4.x)
                   4.0

> 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.0
>
>         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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message