cloud_storage/ducktape: Adjust test for cache size smaller than segment #11773
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
abhijat
force-pushed
the
issues/11449/cache-size-smaller-than-segment-test
branch
from
c535767 to
b0ad535
Compare
|
/ci-repeat 10 |
The test which simulates a cache smaller than the segment size may suffer from timeout failures due to throttling of cache trim. To address this the chunk size is made smaller to reduce trimming frequency, and we read fewer messages in the consumer, just enough that the chunk read path is exercised.
abhijat
force-pushed
the
issues/11449/cache-size-smaller-than-segment-test
branch
from
b0ad535 to
6277f16
Compare
|
/ci-repeat 10 |
jcsp
approved these changes
Jun 29, 2023
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.
The test where cache size is smaller than segment size is adjusted to use a low chunk size to reduce trim frequency. Additionally the count of messages read back by consumer is reduced to read a couple of full segments and not the entire range of messages produced.
FIXES #11449
Does not fix the variant of #11449 where the client makes no progress, but that is tracked separately as a kgo issue
Backports Required
Release Notes