Draft
Conversation
vickenty
reviewed
May 27, 2024
| incr = time.Millisecond * 500 | ||
| } | ||
| w.currentWriteTimeout += incr | ||
| if w.currentWriteTimeout > w.connectTimeout { |
Contributor
There was a problem hiding this comment.
This assumes that connection timeout is larger than the write timeout, although this might not be always the case. Would it make sense to ensure that connectTimeout is at least as big as writeTimeout, or perhaps use a separate upper bound?
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
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.
In order to avoid overloading the agent this gradually increase the
writeTimeoutup to theconnectTimeout.For uds-stream this will also reduce the re-connection rate when the agent is too slow to ingest all the packets, which is important because each new connection comes with a relatively big socket buffer.