Resolve CI failure with longer MaxConnectionAge #556
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.
What this PR does / why we need it:
Resolve CI failure with longer
MaxConnectionAge
.This is to resolve intermittent CI failure, with the assumption that the RPC server's short
MaxConnectionAge
on testing is causing CI failure.Because this solution is based on an assumption, we need to see whether this change will resolve CI failure or not.
Which issue(s) this PR fixes:
Fixes #546
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation:
Checklist: