cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jens Rantil (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-11720) Changing `max_hint_window_in_ms` at runtime
Date Thu, 05 May 2016 13:44:14 GMT
Jens Rantil created CASSANDRA-11720:
---------------------------------------

             Summary: 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


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)

Mime
View raw message