cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Durity, Sean R" <>
Subject RE: merge two cluster
Date Wed, 23 Oct 2019 14:30:56 GMT
Beneficial to whom? The apps, the admins, the developers?

I suggest that app teams have separate clusters per application. This prevents the noisy neighbor
problem, isolates any security issues, and helps when it is time for maintenance, upgrade,
performance testing, etc. to not have to coordinate multiple app teams at the same time. Also,
an individual cluster can be tuned for its specific workload. Sometimes, though, costs and
data size push us towards combining smaller apps owned by the same team onto a single cluster.
Those are the exceptions.

As a Cassandra admin, I am always trying to scale the ability to admin multiple clusters without
just adding new admins. That is an on-going task, dependent on your operating environment.

Also, because every table has a portion of memory (memtable), there is a practical limit to
the number of tables that any one cluster should have. I have heard it is in the low hundreds
of tables. This puts a limit on the number of applications that a cluster can safely support.

Sean Durity – Staff Systems Engineer, Cassandra

Sent: Wednesday, October 23, 2019 6:23 AM
Subject: [EXTERNAL] merge two cluster


I have two cluster and both contains different data sets with different node counts.

Would it be beneficial to merge two cluster?




The information in this Internet Email is confidential and may be legally privileged. It is
intended solely for the addressee. Access to this Email by anyone else is unauthorized. If
you are not the intended recipient, any disclosure, copying, distribution or any action taken
or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed
to our clients any opinions or advice contained in this Email are subject to the terms and
conditions expressed in any applicable governing The Home Depot terms of business or client
engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy
and content of this attachment and for any damages or losses arising from any inaccuracies,
errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature,
which may be contained in this attachment and shall not be liable for direct, indirect, consequential
or special damages in connection with this e-mail message or its attachment.
View raw message