Hi, It may work in some cases, but it shouldn't work in case when client node was disconnected because all the server nodes were down. In this case, when client node will reconnect to the cluster, it will be completely new cluster, that doesn't know anything about old CQs. In this case, you should register CQ again.
Evgenii пн, 8 окт. 2018 г. в 20:24, DanieleBosetti <[email protected]>: > Hi, thanks for replying! > > I double-checked my case, and (I was quite wrong); the client keeps > receiving updates from the CQ after the first server is restarted. > (maybe it could be useful to add a case in the examples section, like > "ContinuousQueryFailover"? I could try doing that eventually) > > > There is a thing that confuses me tough. I find the warning log below > ("Client node was reconnected..") which advises to listen to > EVT_CLIENT_NODE_RECONNECTED. > Does that mean that simply listening to this event is enough for the client > to recover from the disconnection; > or is any further action required if we receive a > EVT_CLIENT_NODE_RECONNECTED (like closing the CQ and re-issuing it) ? > Also, even in presence of this message, my test case still passes (the CQ > keeps pushing data)- > so should I be worried when I see it? > > > "Client node was reconnected after it was already considered failed by the > server topology ..etc.." and > "All continuous queries and remote event listeners created by this client > will be unsubscribed, > consider listening to EVT_CLIENT_NODE_RECONNECTED event to restore them." > > > Thanks! > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
