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

Add a more ops friendly replace_address flag

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Fix Version/s: 1.2.17, 2.0.9, 2.1 rc2
    • Component/s: None
    • Labels:

      Description

      Doing a host replacement with cassandra.replace_address works well, but it is operationally difficult because the flag needs clearing once the replace is successful. Most people will launch through some scripts so remembering to clear the flag is a pain. Forgetting means the node won't come up on a restart.

      We should have a flag like cassandra.replace_address_first_boot that works the same as auto_bootstrap/initial_token: it is totally ignored if the node has successfully bootstrapped but on starting from a clean disk it will work as the existing cassandra.replace_address.

        Attachments

        1. 7356_fix_v2.txt
          2 kB
          Tyler Hobbs
        2. 7356_fix.patch
          0.7 kB
          Marcus Eriksson
        3. 7356.txt
          1 kB
          Brandon Williams

          Activity

            People

            • Assignee:
              brandon.williams Brandon Williams
              Reporter:
              rlow Richard Low
              Reviewer:
              Tyler Hobbs
              Tester:
              Shawn Kumar
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: