If a HotRod client is connected to a server cluster and one of the servers do a correct shutdown, the client keep try to reconnect the server after the cluster view has changed.
From the server-logfile the new cluster view is established
There is no failure from the application perspective, but there there is always a retry if the RoundRobin return the unavailable server.
This might end in a performance or failure issue if there is a larger cluster and a part going out of work for some reason.
This is actually already integrated into 6.3.0
Setting target ER2 so that we know it's already available and it appears in the respective query.
As this was filed against 6.3.0, I'm closing this as NOTABUG. The right fix really made it into 6.3.0.