Fix bug: "timeout_millis" option doesn't work as expected #51
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.
This plugin has
timeout_millis
option but I noticed this option is not set toorg.eclipse.jetty.client.HttpClient
. So fixed it.I tested with Elastic Cloud if this change works as expected.
As a result, many SocketTimeoutException happens when I set 100ms for timeout_millis.
No SocketTimeoutException happens when I set 10000ms for timeout_millis.
Stacktrace before fixed