Okay Thanks. I’ll do some tests
> On Mar 14, 2018, at 2:29 PM, Jeff Jirsa wrote:
>
> I'll confirm that it's worked for me in the past, but you should always test
> changes like this in your lab/qa environment and not rely on some random
> person on the internet.
>
>
> On Wed, Mar 14, 2018 at
I'll confirm that it's worked for me in the past, but you should always
test changes like this in your lab/qa environment and not rely on some
random person on the internet.
On Wed, Mar 14, 2018 at 7:13 AM, Cyril Scetbon
wrote:
> And you confirm that if we use snitches like EC2Snitch or GPFS we
And you confirm that if we use snitches like EC2Snitch or GPFS we’ll only have
to update the seed list in Cassandra.yaml if this node is a seed ?
—
Cyril Scetbon
> On Mar 13, 2018, at 10:08 PM, Jeff Jirsa wrote:
>
> If you're just trying to change an IP, you can just stop the node, change the
If you're just trying to change an IP, you can just stop the node, change
the IP and restart the node and it'll be fine (change it everywhere).
Replacing a node is different: replacing is when a node dies, and you're
replacing it with a new node that doesnt have any data. The
-Dcassandra.replace_a
Hey,
I always thought that changing the IP address of a node requires to use the
same procedure as for a died node, which part of it consists in starting
Cassandra the -Dcassandra.replace_address option as indicated at
https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/opsReplaceNo
