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.

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

Modify startOneNodeRack behavior with 0 target size StS #438

Merged
merged 4 commits into from
Nov 7, 2022

Conversation

burmanm
Copy link
Contributor

@burmanm burmanm commented Oct 28, 2022

What this PR does:

  • Modify decommission test to use 2 racks per dc (and Cassandra 4.0.6)
  • Modify startOneNodeRack to skip StatefulSets which have 0 target nodes, such as during decommission

Which issue(s) this PR fixes:
Fixes #437

Checklist

  • Changes manually tested
  • Automated Tests added/updated
  • Documentation added/updated
  • CHANGELOG.md updated (not required for documentation PRs)
  • CLA Signed: DataStax CLA

… modify startOneNodeRack to skip StatefulSets which have 0 target nodes, such as during decommission
@burmanm burmanm requested a review from a team as a code owner October 28, 2022 14:50
@burmanm burmanm merged commit 0d559ee into k8ssandra:master Nov 7, 2022
emerkle826 pushed a commit to emerkle826/cass-operator that referenced this pull request Dec 1, 2022
* Modify decommission test to use 2 racks per dc (and Cassandra 4.0.6), modify startOneNodeRack to skip StatefulSets which have 0 target nodes, such as during decommission

* Fix filename in the decommission test

* Remove erroneous characters from testdata file

* Datacenter might not be healthy during decommission
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

K8SSAND-1863 ⁃ startOneNodeRack does not handle decommissioned StatefulSets
2 participants