Hello! You can just set clientReconnectEnabled to false. Then, if it is out of topology, just start a new one to make sure you have a fresh start.
Not sure about other events. Maybe handle ACTIVATED/DEACTIVATED? Regards, -- Ilya Kasnacheev вт, 13 окт. 2020 г. в 14:49, VeenaMithare <v.mith...@cmcmarkets.com>: > Thanks Ilya, > > >>I don't think so. Node can reconnect to a *different* cluster, or it may > be disconnected for a while and return to the same cluster. For client > node, > segmented/disconnected difference is not relevant. Neither it is for server > node, in fact. > > In that case, we will have the same handler for segmented and reconnected > events. The handler will restart ignite and deploy any continuous queries > as > needed. > Thank you for this guidance. > > Does the server or the client need to have a handler for any other 'cluster > specific' events ? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
