If node with CQ leave grid (or just reconnect to grid, if it client node) - you should recreate CQ, because some cache updates can happen when node with CQ listener can't receive it. What happen it this case: 1) Node with changed cache entry process CQ, entry pass remote filter and node try to send continues query event message to CQ node 2) If sender node can't push msg by any reasons (sender will retry few times) - it can't wait receiver too long and drop it. 3) After CQ node return to the cluster - it must recreate CQ to process initialQuery to get such events. If you sure that no CQ owners node leaves grid - we need to continue, becouse it can be bug. And yes, I think that it is not evidently that you must recreate CQ after client reconnect, but that is how ignite work now.
2017-05-05 16:56 GMT+07:00 begineer <redni...@gmail.com>: > Umm. actually nothing get logged in such scenario. However, as you > indicated > earlier, I could see trades get stuck if a node leaves the grid(not > always). > Do you know why that happens? Is that a bug? > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Continuous-Query-remote-listener-misses-some-events- > or-respond-really-late-tp12338p12452.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
