On Wed, Feb 27, 2019 at 4:15 AM wxn...@zjqunshuo.com
wrote:
> >After restart with the new address the server will notice it and log a
> warning, but it will keep token ownership as long as it keeps the old host
> id (meaning it must use the same data directory as before restart).
>
> Based on my
Hi Alex,
>After restart with the new address the server will notice it and log a
>warning, but it will keep token ownership as long as it keeps the old host id
>(meaning it must use the same data directory as before restart).
Based on my understanding, token range is binded to host id. As long
On Tue, Feb 26, 2019 at 3:26 PM Durity, Sean R
wrote:
> This has not been my experience. Changing IP address is one of the worst
> admin tasks for Cassandra. System.peers and other information on each nodes
> is stored by ip address. And gossip is really good at sending around the
> old informati
This has not been my experience. Changing IP address is one of the worst admin
tasks for Cassandra. System.peers and other information on each nodes is stored
by ip address. And gossip is really good at sending around the old information
mixed with new…
Sean Durity
From: Oleksandr Shulgin
S
On Tue, Feb 26, 2019 at 9:39 AM wxn...@zjqunshuo.com
wrote:
>
> I'm running 2.2.8 with vnodes and I'm planning to change node IP address.
> My procedure is:
> Turn down one node, setting auto_bootstrap to false in yaml file, then
> bring it up with -Dcassandra.replace_address. Repeat the procedur
Hi All,
I'm running 2.2.8 with vnodes and I'm planning to change node IP address.
My procedure is:
Turn down one node, setting auto_bootstrap to false in yaml file, then bring it
up with -Dcassandra.replace_address. Repeat the procedure one by one for the
other nodes.
I care about streaming bec
