Issue #180 When creating new cluster, Casskop starts with 1 node per rack, then continue with scaling-out racks #183
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
increase reusability by extracting smaller methods
reduced number of unnecessary sleep during tests
refactor: initializingSubPhase in status (preparation for handling big clusters from scratch)
creating new cluster: start with 1 node/rack, then scale-out to desired size Fixes cscetbon#180
pchmieli
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's in this PR?
When creating new cluster, Casskop starts with 1 node per rack, then continue with scaling-out racks
Why?
To avoid error when creating (from scratch) cluster with
nodePerRacks >= 2 && racks >= 3Details in issue #180
Checklist