tests: extend consumer timeout in test with kills #6478
Merged
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
test_write_with_node_failures randomly kills nodes while a verifiable consumer is running against the cluster. Hence, the consumer group members need to react to the broker failures. If we get unlucky, and the test continously kills the group coordinator broker, then there may be long periods of time when no data is consumed. This non-determinism coupled with a short consumer timeout (30s) makes the test flaky. This commit increases the consumer timeout to 90s in order to increase the chances of all the required data being consumed before the timeout.
jcsp
approved these changes
Sep 20, 2022
|
/backport v22.2.x |
|
/backport v22.1.x |
|
/backport v21.11.x |
This was referenced Sep 20, 2022
|
Failed to run cherry-pick command. I executed the below command: |
mmedenjak
added
kind/bug
This pull request was closed.
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.
Cover letter
test_write_with_node_failures randomly kills nodes while a verifiable consumer is running against the cluster. Hence, the consumer group members need to react to the broker failures. If we get unlucky, and the test continously kills the group coordinator broker, then there may be long periods of time when no data is consumed. This non-determinism coupled with a short consumer timeout (30s) makes the test flaky.
This commit increases the consumer timeout to 90s in order to increase the chances of all the required data being consumed before the timeout.
Fixes #4639
Backport Required