when changing between leader and follower re-attempt connecting to circumvent OS resource shortages #10243
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.
The resilient testsuites family frequently disconnects from leader / follower to work out test states.
This may lead to instability in tests if the system fails to connect in one of these reconnects.
Known popular reasons for failing connects are IP-Port shortages.
To circumvent testfailure this PR will re-attempt connecting to the SUT after an increasing grace period several times.
Example of such a failed testrun: