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

flush before shutdown so restart is faster

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

Details

    • New Feature
    • Status: Resolved
    • Low
    • Resolution: Later
    • None
    • Packaging
    • None

    Description

      Cassandra handles flush in its shutdown hook for durable_writes=false CFs (otherwise we're guaranteed to lose data) but leaves it up to the operator otherwise. I'd rather leave it that way to offer these semantics:

      • cassandra stop = shutdown nicely [explicit flush, then kill -int]
      • kill -INT = shutdown faster but don't lose any updates [current behavior]
      • kill -KILL = lose most recent writes unless durable_writes=true and batch commits are on [also current behavior]

      But if it's not reasonable to use nodetool from the init script then I guess we can just make the shutdown hook flush everything.

      Attachments

        Activity

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

          People

            brandon.williams Brandon Williams Assign to me
            jbellis Jonathan Ellis
            Brandon Williams
            paul cannon
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment