-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Propagate client thumbstone when a client creation fails #221
Conversation
f4c2727
to
5235028
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm okay with the changes.
Maybe it worth to add a test with the default socket provider (don't sure either catch real 'connection refuse' error or mock get() method). It also seems that it worth to test the cluster client with its default socket provider (this is the case on which a customer asks us how to check what is going wrong). After that we'll sure that a user will see a real reason in case of some connectivity problems (during a first connection as well as during a reconnection later).
5235028
to
868b377
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would find ConnectException where it is in causes just in case. Other then that I'm okay. LGTM.
6e93879
to
ab1c2f6
Compare
I'm ok. |
ab1c2f6
to
ed99a9b
Compare
Propagate client thumbstone when a client creation fails
Closes: #30