-
Notifications
You must be signed in to change notification settings - Fork 589
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tests: update partition limits #9257
Conversation
In 3e3975b the default topic_partitions_per_shard changed to 1000: the test was previously working because the configured limit was so much higher than the test's limit. The internal_partition_slack value was probably set before we changed the default number of consumer offsets partitions to 16.
This was exceeding the 1000 partitions per core limit. It was getting away with it because it is a relatively low traffic test compared with ManyPartitionsTest. Revise its partition count to fit within the supported max.
/cdt tests/rptest/scale_tests/many_partitions_test.py tests/rptest/scale_tests/partition_balancer_scale_test.py |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The cdt runs seemed to have trouble kicking off -- I retried the regular build, and maybe we can retry the cdt run once that passes (assuming the issue is with ordering). Opened https://github.com/redpanda-data/vtools/issues/1561 for it
partitions_count = 1000 * self.redpanda.get_node_cpu_count() * len( | ||
self.redpanda.nodes) - 32 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we be dividing by the replication factor?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, itchy merge finger -- I think was looking at a github view that had updated test statuses but not shown comments.
You are right! Followup PR here #9274
Change 3e3975b caused some scale tests to fail https://ci-artifacts.dev.vectorized.cloud/vtools/0186a681-02da-49ac-8a24-e33caa78970f/vbuild/ducktape/results/2023-03-03--001/report.html
These limits need updating so that the tests operate within the supported range. ManyPartitionsTest was only out by a few, partition balancer test was further out.
Backports Required
Release Notes