Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Do NOT restart after Cassandra nodes are added or removed due to scale events #14

Open
bradfordcp opened this issue Mar 17, 2021 · 3 comments
Open

Do NOT restart after Cassandra nodes are added or removed due to scale events #14

bradfordcp opened this issue Mar 17, 2021 · 3 comments
Labels
cass-operator k8ssandra

Comments

@bradfordcp
Copy link
Member

Changing the size parameter should not result in a rolling restart of cluster nodes.
@Orhideous
Copy link

Is this bug still relevant?

@jsanda
Copy link

jsanda commented Aug 17, 2021

Unfortunately it is due to this line https://github.com/k8ssandra/k8ssandra/blob/main/charts/k8ssandra/templates/cassandra/cassdc.yaml#L156. When the size is changed, we might end up changing the replication factor of system keyspaces. That will cause an update to the StatefulSet after the scaling which triggers the rolling restart. Of course k8ssandra shouldn't blindly change the replication factor once the cluster has been created.

@jsanda
Copy link

jsanda commented Aug 17, 2021

@Orhideous see k8ssandra/k8ssandra#445

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cass-operator k8ssandra
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bradfordcp @jsanda @Orhideous