Adjusting Retry Max Delay default value to 5 seconds. #151
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
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.
Pull Request check list
Affected functionality
Description of change
Adjusting Retry Max Delay default value to 5 seconds.
Given the context of the Workload API listening on a local socket and likely serving a limited number of workloads, adjusting the Retry Max Delay default value to a more reasonable value, such as 5 seconds, can enhance efficiency and responsiveness. This adjustment acknowledges the balance between providing timely updates and not overly taxing the system resources or flooding the Workload API with requests during periods of rapid changes or temporary issues.
Which issue this PR fixes