Thank you for your email. I will get back to you soon.
Thanks for taking the time to respond. I appreciate the insights greatly.
Agreed on the point about adding complexity for the same
functionality/performance, as well as the point on bespoke-ness and difficulty.
ECS resource limits are something we’ll look into. The ECS deployment method is
also
I completely missed that this ECS != EKS. My brain flipped a few bits
there.
I have never run C* on ECS and I can't imagine I ever would. It seems like
the most bespoke and difficult way to run it.
+1 to everything Patrick said.
Jon
On Thu, Jun 12, 2025 at 12:46 PM Patrick McFadin wrote:
>
I feel like I should weigh in here. :) Running C* on Kubernetes is best
coming from Kubernetes and adding C*. It's a mentality thing. "Why can't I
log into my nodes??" There is a book exactly for this topic:
https://www.oreilly.com/library/view/managing-cloud-native/9781098111380/
At Datastax, we r
Hi Daemeon,
Firstly, apologies to everyone in the thread as I’m not comparing EC2 against
K8s but specifically against Elastic Container Service backed by EC2.
Thanks for the response. I agree that running persisted databases on K8s does
not seem ideal. Although there has been a lot of work on
What operator are you all using? We've just been using statefulsets for
our clusters. I'm a big time on-hardware fan, but an issue with
Cassandra is the notion of one JVM per about 1 to 2TBytes of disk
space. Most large servers are in the 256 core+ / 100+TBytes of disk.
Managing that many i
Years ago (before K8S) yes. Found it useful for CI/CD pipelines (because
the ECS containers could be suspended without loss of data). Found it an
antipattern because of AWS was prone to over-provision the hardware,
resulting in (almost) invisibly slow containers vs. (almost) invisibly
faster contai
K8S has some key use cases where it is ideal, and some use cases that are
more nuanced, and some that are anti-patterns. It is my opinion that
services like C*, Hadoop, Kafka, and persisted distributed databases are
certainly not ideal. I admit to a prejudice of having worked with K8S since
before
As a follow-up, do you have any thoughts on running Cassandra on ECS (Elastic
Container Service) itself? We haven’t seen any examples or recommendations for
or against it out there, but you’ve seen lots of different deployments in the
wild.
From: Jon Haddad
Date: Thursday, June 12, 2025 at 7:1
Thank you all for your thoughts. They are greatly appreciated!
It seems that some of your thoughts echo our worries about there being
additional hidden nuances to implementing the same level of functionality and
reliability in ECS and even K8s. We agree that the K8ssandra operator would be
the
I agree that managing Cassandra on Kubernetes can be challenging without
prior experience, as understanding all the nuances of Kubernetes takes time.
However, there are ways to address the rescheduling issues, node placement,
and local disk concerns that were mentioned. You can pin pods to specifi
Quick correction on my previous message — I assumed you were referring
to running Cassandra on Kubernetes, not purely ECS.
Many of the same concerns still apply. ECS tasks can also be
rescheduled or moved between instances, which poses risks for
Cassandra’s rack awareness and replica distribution.
I usually advise against running Cassandra (or most databases) inside
Kubernetes. It might look like it simplifies operations, but in my
experience, it tends to introduce more complexity than it solves.
With Cassandra specifically, Kubernetes may reschedule pods for
reasons outside your control (e
13 matches
Mail list logo