ch I am trying to get to the bottom of. I am not
> fully au fait with Ansible and we are also using Ans. Tower which allows
> for more flexibility so here should be some practical options.
>
>
>
> *From:* Durity, Sean R
> *Sent:* Thursday, June 2, 2022 7:04 PM
> *To:* user@cassan
bottom of. I am not fully au
fait with Ansible and we are also using Ans. Tower which allows for more
flexibility so here should be some practical options.
From: Durity, Sean R
Sent: Thursday, June 2, 2022 7:04 PM
To: user@cassandra.apache.org
Subject: RE: Topology vs RackDC
EXTERNAL
I agree; it
@cassandra.apache.org
Subject: [EXTERNAL] Re: Topology vs RackDC
It really depends on how do you manage your nodes. With automation tools, like
Ansible, it's much easier to manage the rackdc file per node. The "master list"
doesn't need to exist, because the file is written
that a change in topology requires
the distribution of a new file and a rolling restart.
Long live the PropertyFileSnitch! 😉
Sean R. Durity
*From:* Paulo Motta
*Sent:* Thursday, June 2, 2022 8:59 AM
*To:* user@cassandra.apache.org
*Subject:* [EXTERNAL] Re: Topology vs RackDC
It think topology
(slight) penalty that a change in topology requires the distribution of a new
file and a rolling restart.
Long live the PropertyFileSnitch! 😉
Sean R. Durity
From: Paulo Motta
Sent: Thursday, June 2, 2022 8:59 AM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Re: Topology vs RackDC
It
Agree with Paulo on this one.
If you're running a cluster on K8s, in the cloud, or under some other
conditions in which IPs change, the cassandra-topology.properties file is
going to quickly become a burden. Especially if that cluster has more than
just a few nodes.
Increasing your cluster from
It think topology file is better for static clusters, while rackdc for
dynamic clusters where users can add/remove hosts without needing to update
the topology file on all hosts.
On Thu, 2 Jun 2022 at 09:13 Marc Hoppins wrote:
> Hi all,
>
> Why is RACKDC preferred for production than TOPOLOGY?
>
Hi all,
Why is RACKDC preferred for production than TOPOLOGY?
Surely one common file is far simpler to distribute than deal with the
mucky-muck of various configs for each host if they are in one rack or another
and/or one datacentre or another? It is also fairly self-documenting of the
setup
