.
From: Alexander Dejanovski
Sent: Wednesday, February 27, 2019 9:22 AM
To: user@cassandra.apache.org
Subject: Re: [EXTERNAL] Re: Question on changing node IP address
It has to be balanced with the dangers related to the PropertyFileSnitch.
I've seen such incidents happen twice in the las
On Wed, Feb 27, 2019 at 3:11 PM Durity, Sean R
wrote:
> We use the PropertyFileSnitch precisely because it is the same on every
> node. If each node has to have a different file (for GPFS) – deployment is
> more complicated. (And for any automated configuration you would have a
> list of hosts an
It has to be balanced with the dangers related to the PropertyFileSnitch.
I've seen such incidents happen twice in the last few months in different
places and both times recovery was difficult and hazardous.
I still strongly recommend against it.
On Wed, Feb 27, 2019 at 3:11 PM Durity, Sean R
wr
We use the PropertyFileSnitch precisely because it is the same on every node.
If each node has to have a different file (for GPFS) – deployment is more
complicated. (And for any automated configuration you would have a list of
hosts and DC/rack information to compile anyway)
I do put UNKNOWN as
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
