release-25.4: workload: reduce yscb setup batch size#170957
Merged
trunk-io[bot] merged 1 commit intoMay 26, 2026
Merged
Conversation
`TestAllRegisteredSetup/ycsb` can run under an external-process test tenant. YCSB's default setup path uses 1000-row `INSERT` batches, and because YCSB places each field in its own column family, each batch fans out to a large number of KV writes. In overloaded CI runs, that can starve SQL liveness heartbeats long enough for the tenant to shut down, surfacing as setup failures such as "sql: database is closed". Cap only the YCSB `InsertsDataLoader` batch size in `TestAllRegisteredSetup`. This keeps the test exercising the same workload and tenant mode while reducing the size of each setup write batch. This does not change YCSB workload defaults or benchmark/import behavior outside this test. Epic: none Fixes: #170911, #169034, #168946 Release note: None
blathers-crl
Bot
requested review from
cpj2195 and
shailendra-patel
and removed request for
a team
Author
|
Thanks for opening a backport. Before merging, please confirm that it falls into one of the following categories (select one):
Add a brief release justification to the PR description explaining your selection. Also, confirm that the change does not break backward compatibility and complies with all aspects of the backport policy. All backports must be reviewed by the TL and EM for the owning area. |
Contributor
|
😎 Merged directly without going through the merge queue, as the queue was empty and the PR was up to date with the target branch - details. |
blathers-crl
Bot
added
backport
Member
|
This change is |
golgeek
approved these changes
May 26, 2026
blathers-crl
Bot
added
the
backport-test-only
Contributor
|
/trunk merge |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Backport 1/1 commits from #170934 on behalf of @golgeek.
TestAllRegisteredSetup/ycsbcan run under an external-process test tenant. YCSB's default setup path uses 1000-rowINSERTbatches, and because YCSB places each field in its own column family, each batch fans out to a large number of KV writes.In overloaded CI runs, that can starve SQL liveness heartbeats long enough for the tenant to shut down, surfacing as setup failures such as "sql: database is closed".
Cap only the YCSB
InsertsDataLoaderbatch size inTestAllRegisteredSetup. This keeps the test exercising the same workload and tenant mode while reducing the size of each setup write batch. This does not change YCSB workload defaults or benchmark/import behavior outside this test.Epic: none
Fixes: #170911, #169034, #168946
Release note: None
Release justification: test only change