Description of problem: If the complete cluster is going down for some reason, the client side throws TransportExceptions. If the client continue in this state without a restart there are the following issues: - the last node need to be started to continue - the cluster view will not be updated any more - client continue only with the 'last' node no matter whether the cluster topology will be changed on the server side
Galder Zamarreño <galder.zamarreno> updated the status of jira ISPN-5283 to Coding In Progress