allow config of connection timeout and error limit #1758
Merged
Conversation
This file contains hidden or 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
chouetz
approved these changes
Oct 24, 2025
usamasaqib
approved these changes
Oct 24, 2025
brycekahle
force-pushed
the
bryce.kahle/configure-connection-retry
branch
from
3d80307 to
9f0858f
Compare
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
Tests failed on this commit 0b27190: What to do next?
|
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
dd-devflow
bot
added
mergequeue-status: queued
mergequeue-status: in_progress
and removed
mergequeue-status: rejected
mergequeue-status: queued
labels
dd-devflow
bot
added
mergequeue-status: done
and removed
mergequeue-status: in_progress
labels
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.
What does this PR do?
Adds configuration for connection dial error limit and per-dial error timeout in seconds.
Which scenarios this will impact?
aws/ec2
aws/microVMs
azure
gcp
hyperv
Motivation
In some situations including local microvms, waiting 8 minutes (500s) for failure is too long.
Additional Notes