cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-7356) Add a more ops friendly replace_address flag
Date Wed, 25 Jun 2014 15:33:25 GMT


Tyler Hobbs updated CASSANDRA-7356:

    Attachment: 7356_fix_v2.txt

7356_fix_v2 moves the check for replacing after having already bootstrapped instead of removing
it entirely.  I put this through a few bootstrap, replace_address, and replace_address_first_boot
tests with ccm locally.

> Add a more ops friendly replace_address flag
> --------------------------------------------
>                 Key: CASSANDRA-7356
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Richard Low
>            Assignee: Brandon Williams
>             Fix For: 1.2.17, 2.0.9, 2.1 rc2
>         Attachments: 7356.txt, 7356_fix.patch, 7356_fix_v2.txt
> 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.

This message was sent by Atlassian JIRA

View raw message