Chadha<mailto:manu.cha...@hotmail.com>
Sent: 08 October 2020 13:33
To: user@cassandra.apache.org<mailto:user@cassandra.apache.org>
Subject: RE: Reducing no. of nodes to 0 without losing data
Dear Christopher
I tried the answer and it works (at least the stopping bit). I still need to
te
ober 2020 05:47
To: user@cassandra.apache.org<mailto:user@cassandra.apache.org>
Subject: Re: Reducing no. of nodes to 0 without losing data
cass-operator has a parameter spec.stopped (
https://github.com/datastax/cass-operator/blob/master/operator/example-cassdc-yaml/cassandra-3.11.x/exampl
com/fwlink/?LinkId=550986> for Windows 10
From: Oleksandr Shulgin<mailto:oleksandr.shul...@zalando.de>
Sent: 08 October 2020 05:40
To: User<mailto:user@cassandra.apache.org>
Subject: Re: Reducing no. of nodes to 0 without losing data
On Thu, Oct 8, 2020 at 12:21 AM Manu Chadha
mailt
I stand corrected. Happy to be schooled by one of the authors of
cass-operator. :)
On Thu, 8 Oct 2020 at 15:54, Christopher Bradford
wrote:
> This isn’t really a scaling operation. It’s a start / stop operation. In
> my mind scaling the cluster would change the tokens / replicas. Here the
> requ
This isn’t really a scaling operation. It’s a start / stop operation. In my
mind scaling the cluster would change the tokens / replicas. Here the
request seems to be all or nothing.
On a side note scale down operations were merged 3 days ago in PR #265 (
https://github.com/datastax/cass-operator/p
cass-operator has a parameter spec.stopped (
https://github.com/datastax/cass-operator/blob/master/operator/example-cassdc-yaml/cassandra-3.11.x/example-cassdc-full.yaml#L65)
when set to true the underlying stateful sets are scaled down to 0 while
keeping the persistent volumes. This allows you to
The cass-operator does not support scaling down at this point, only scaling
up. So the operation you're after isn't possible. Cheers!
>
On Thu, Oct 8, 2020 at 12:21 AM Manu Chadha wrote:
> Hi
>
>
>
> I have created a Cassandra cluster on Kubernetes using cass-operator on
> gcp. It is for my personal experimentation. To avoid incurring cost, I
> want to stop the cluster when I am not using it and start it when I need it
> without
Hi
I have created a Cassandra cluster on Kubernetes using cass-operator on gcp. It
is for my personal experimentation. To avoid incurring cost, I want to stop the
cluster when I am not using it and start it when I need it without losing data.
Is there a way to do so? Would setting number of siz
