ReconnectingClient prints "Lost connection" for old nodes when another one is added - while requests go through just fine about folsom

[spkrka]

Thanks for the report! It sounds it's possible that the old clients are still trying to reconnect. I'll investigate it further.

[spkrka]

Actually... looks like this is intentional. When reconnecting, there's a 60 second shutdown delay by default: https://github.com/spotify/folsom/blob/master/folsom/src/main/java/com/spotify/folsom/ketama/SrvKetamaClient.java#L206

You can reconfigure the shutdown delay if you want.

[alexeyOnGitHub]

right, my point is specifically about the log message.
I was thinking maybe the log message could be changed to make it explicit that the connection was not suddenly lost, but it was due to the planned shutdown. e.g. check if (shutdown) ... and then print different messages depending on whether it is a sudden connection loss vs. planned shutdown.

the message is somewhat confusing and scary otherwise.

[spkrka]

I'll look into how much work it would be to introduce pending shutdowns and silence the logs for those.