Tune Cassandra options for faster startup #4309
Merged
Conversation
This file contains 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
kiview
approved these changes
Jul 28, 2021
bsideup
commented
Jul 28, 2021
| @@ -58,8 +58,15 @@ public CassandraContainer(DockerImageName dockerImageName) { | |||
| dockerImageName.assertCompatibleWith(DEFAULT_IMAGE_NAME); | |||
|
|
|||
| addExposedPort(CQL_PORT); | |||
| setStartupAttempts(3); | |||
There was a problem hiding this comment.
this was never necessary and only hid the problem
|
@kiview yep! (are you also thinking about BitBucket? ;)) |
bsideup
commented
Jul 28, 2021
Comment on lines
+68
to
+69
| withEnv("HEAP_NEWSIZE", "128M"); | ||
| withEnv("MAX_HEAP_SIZE", "1024M"); |
There was a problem hiding this comment.
by default, Cassandra will be allocating 10Gb of RAM or so - obviously not necessary for testing
rnorth
approved these changes
Aug 3, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We never attempted at tuning Cassandra options to make it start faster. Apparently, there are a few low hanging fruits (focused on single-node scenario) that make it start significantly faster:
Before:
After: