Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
connection exception logged after client disconnects in ClientListenerSupport #9709
The class has the following method:
what the reason to log error stack in the exception catch section? It is expected that client will not able to reconnect, right? Is it possible to change it to:
, just to prevent unnecessary error logs on the client side?
If client is shutdown by user with
When client itself could not connect and give up, it should be a warning, because it is not intentional. The cluster that expected to be there is gone.
Although I agree with stacktrace is not giving extra inside, exception message has information about tried addresses. So we can convert to following to get rid of stacktrace , but I think warning should stay.