showuon opened a new pull request #8885: URL: https://github.com/apache/kafka/pull/8885
This flaky test exists for a long time, and it happened more frequently recently. In KAFKA-8264 and KAFKA-8460, it described the issue for this test is that > Timed out before consuming expected 2700 records. The number consumed was xxxx I did some investigation. This test is to test: we consume all partitions if fetch max bytes and max.partition.fetch.bytes are low. And what it did, is to create 3 topics and 30 partitions for each. And then, iterate through all 90 partitions to send 30 records for each. Finally, verify the we can consume all the records successfully. What the error message saying is that it cannot consume all the records in time (might be the busy system) So, we can actually decrease the record size to avoid it. I checked all the error messages we collected in KAFKA-8264 and KAFKA-8460, the failed cases can always consume at least 1440 up (total is 2700). So, I set the records half size of the original setting, it'll become 1350 records in total. It should make this test more stable. ### Committer Checklist (excluded from commit message) - [ ] Verify design and implementation - [ ] Verify test coverage and CI build status - [ ] Verify documentation (including upgrade notes) ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
