cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mck (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11720) Changing `max_hint_window_in_ms` at runtime
Date Tue, 08 Nov 2016 22:50:59 GMT


mck commented on CASSANDRA-11720:


Some small feedback [~ztyx]:
  • can we add a test?
      ∘  dtest ( (or a unit test if something can be created…)
  • the docs need to be updated
      ∘ we'd need an entry in {{doc/build/html/tools/nodetool/nodetool.html}}

> Changing `max_hint_window_in_ms` at runtime
> -------------------------------------------
>                 Key: CASSANDRA-11720
>                 URL:
>             Project: Cassandra
>          Issue Type: Wish
>          Components: Coordination
>            Reporter: Jens Rantil
>            Priority: Minor
>              Labels: lhf
>         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

View raw message