[ https://issues.apache.org/jira/browse/CASSANDRA-11720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
mck resolved CASSANDRA-11720. ----------------------------- Resolution: Fixed Committed. I don't have access to push to riptano/cassandra-dtest so i've opened a pull request to get the new dtest in. https://github.com/riptano/cassandra-dtest/pull/1470 [~jjirsa], is that something you can fix for me? > 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