CI: cassandra workflow: bigger prepared cache #1188
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
Some tests exhibit flakiness when run against Cassandra, returning DbError::Unprepared. As an attempt to combat the flakiness, the prepared statements cache size is increased in the docker compose script. The default is MAX(10MiB, heap_size / 256). 100MB is the first guess; let's see if it's enough.
|
|
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.
Some tests (notably:
test_coalescing- #864) exhibit flakiness when run against Cassandra, returningDbError::Unprepared. As an attempt to combat the flakiness, the prepared statements cache size is increased in the docker compose script.The default is
MAX(10MiB, heap_size / 256). 100MB is the first guess; let's see if it's enough.Fixes: #864
(hopefully)
Pre-review checklist
[ ] I added relevant tests for new features and bug fixes.[ ] I have provided docstrings for the public items that I want to introduce.[ ] I have adjusted the documentation in./docs/source/.Fixes:annotations to PR description.