Hi Alex, Thank you for the reply . >> verify the continuous query definitions using the appropriate view: https://apacheignite.readme.io/docs/continuous_queries
We are on 2.7.6 version. I guess this view is not available for us. Also we have been running the CQs for couple of months now in our test env. and have not faced any issues. This issue is more recent and happens sometimes ( cannot figure out what could have caused it yet. ) . Though the issue has happened couple of times on our test env. - I am not able to reproduce this on my local machine. Also `i was able to cause this failure only once on the linux test env ( never so far on my windows machine even though I have tested many scenarios so far. ) It looks like some exceptional scenario or some race condition has caused this. Please note that we have recently put a EVT_NODE_SEGMENTED HANDLER and we have a handler to a cluster switch request where switch to a different cluster based on updates on a particular record on a particular table- the handling of both events is to do ignite.close() and Ignition.start()( with the right cluster config ). As mentioned, we have tested the event handler and huge inserts/updates after segmentation etc. and I am not able to cause this issue to occur. regards, Veena -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
