is
> not a limit there.
>
>
>
> Best,
>
> Raymond Yu
>
>
>
> *From: *Jon Haddad
> *Date: *Thursday, June 12, 2025 at 12:50 PM
> *To: *user@cassandra.apache.org
> *Subject: *Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS
>
> *This Message
Thank you for your email. I will get back to you soon.
: user@cassandra.apache.org
Subject: Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS
This Message is From an External Sender
Caution: Do not click links or open attachments unless you recognize the sender
and know the content is safe.
I completely missed that this ECS != EKS. My brain
al, given an existing Cassandra EC2 footprint and experience
>> deploying in that fashion, we’re looking for points for or against
>> deploying Cassandra on ECS if in-house tooling is also needed, as outside
>> opinions were desired.
>>
>>
>>
>> Best,
>>
t; Best,
>
> Raymond Yu
>
>
>
>
>
>
>
> *From: *daemeon reiydelle
> *Date: *Thursday, June 12, 2025 at 9:42 AM
> *To: *user@cassandra.apache.org
> *Subject: *Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS
>
> *This Message is From an Extern
.
Best,
Raymond Yu
From: daemeon reiydelle
Date: Thursday, June 12, 2025 at 9:42 AM
To: user@cassandra.apache.org
Subject: Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS
This Message is From an External Sender
Caution: Do not click links or open attachments unless you recognize the
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
June 12, 2025 at 7:16 AM
> *To: *user@cassandra.apache.org
> *Subject: *Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS
>
> *This Message is From an External Sender*
> Caution: Do not click links or open attachments unless you recognize the
> sender and know the
t; *From: *Jon Haddad
> *Date: *Thursday, June 12, 2025 at 7:16 AM
> *To: *user@cassandra.apache.org
> *Subject: *Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS
>
> *This Message is From an External Sender*
> Caution: Do not click links or open attachments unle
:16 AM
To: user@cassandra.apache.org
Subject: Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS
This Message is From an External Sender
Caution: Do not click links or open attachments unless you recognize the sender
and know the content is safe.
I agree that managing Cassandra on
in the Cassandra community from the K8ssandra operator,
we have significantly more worries with using an in-house one.
From: Jon Haddad
Date: Thursday, June 12, 2025 at 7:16 AM
To: user@cassandra.apache.org
Subject: Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS
This Message is From
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
It's possible to manage Cassandra well both with VMs and containers.
As you'd be running one container per VM, there is no significant
advantage for
containers. K8s provides nice tooling and some methodological enforcement
which
brings order to the setup but if the team aren't top notch experts in
15 matches
Mail list logo
