When the xml configuration file of the ignite cluster changes, the cluster stops, and the cluster needs to be restarted. After the startup, because the cluster is configured with the baseline, the cluster is automatically activated after the restart, but the client connection will be, prompting deactived to re-activate, the client After the terminal fails to start, after the cluster is activated, the client can connect normally. This problem occurs after the 2.3 version. Is there any solution?
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: when cluster restart then client need deactived
It hard to tell from your explanation what is the exact problem. Is it the
client which cannot connect to the cluster while it is the middle of the
activation process? Anyway, could you share the logs from all nodes (client
logs as well)? It will help to understand the problem.