Increase response-timeout for big snapshot tests #577
Merged
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.
https://github.com/RedisLabs/redisraft/actions/runs/3991700932/jobs/6846775748
Ran this test with trace level logs, looks like due to extreme slow-down on MacOS instance, followers send snapshot message responses after a second. Default
response-timeout
is 1 second. So, leader node marks the request failed and retries. It takes quite a time to finish snapshot delivery, sometimes test fails due towait_for_unanimity()
timeout which is 20 seconds.For the two tests that use big snapshots, this PR increases
response-timeout
to 5 seconds.