As far as I understant you create CQ in Service.init, so node with running service is CQ node. All other nodes from grid will send CQ events to this node to process in your service and if you don't configure nodeFilter for service - any node can run it, so any node can be CQ node. But it shouldn't be a problem if you create CQ in Service.init() and haven't too heavy load on you cluster (anyway if data owner node failed to deliver messages to node with running service (CQ node) - you should see it in logs). If you give some code examples how you use CQ - I can say more.
2017-05-05 17:59 GMT+07:00 begineer <redni...@gmail.com>: > Thanks, In my application, all nodes are server nodes > And how do we be sure that nodes removed/ reconnect to grid is CQ node, it > can be any. > Also, Is this issue possible in all below scenarios? > 1. if node happens to be CQ node or any node? > 2. node is removed from grid forcefully(manual shutdown) > 3. node went down due to some reason and grid dropped it > > 3rd one looks like safe option since it is dropped by grid so grid should > be > ware where to shift the CQ? Please correct me if I am wrong. > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Continuous-Query-remote-listener-misses-some-events- > or-respond-really-late-tp12338p12454.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
