There are cases supporting both sides. I can see the benefits of the more
dynamic setup.
However, how do you ansible/automate when you have multiple switches in 2 or
more datacentres and all your nodes are in the same VLAN or VLANs? This is the
sticking point which I am trying to get to the bot
I agree; it does depend. Our ansible could not infer the DC name from the
hostname or ip address of our on-prem hardware. That’s especially true when we
are migrating to new hardware or OS and we are adding logical DCs with
different names. I suppose it could be embedded in the ansible host file
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 once and will never get updated. The automation tool will create
nodes based on the r
I agree with Marc. We use the cassandra-topology.properties file (and
PropertyFileSnitch) for our deployments. Having a file different on every node
has never made sense to me. There would still have to be some master file
somewhere from which to generate that individual node file. There is the
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
