Uploaded image for project: 'Apache Cassandra'
  1. Apache Cassandra
  2. CASSANDRA-11720

Changing `max_hint_window_in_ms` at runtime

Agile BoardAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      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.

      Attachments

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            hnishi Hiroyuki Nishi Assign to me
            ztyx Jens Rantil
            Hiroyuki Nishi
            Michael Semb Wever
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment