fix: add java.net.ConnectException to the list of errors that force h… #65
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
…andling the error in the client so if during the usage of a node, the client would mark it as unhealthy if it just is not reachable.
|
Thanks for the quick PR! |
|
YW!! Even better though. Actually i was going to update the PR cause we got some Going to close this one |
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.
…andling the error in the client so if during the usage of a node, the client would mark it as unhealthy if it just is not reachable.
Fix for #64
Change Summary
Added java.net.ConnectException to the list of errors that force handling the erorr in the client
PR Checklist