ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vkulichenko <valentin.kuliche...@gmail.com>
Subject Re: How to avoid the event lost in the continuous query
Date Mon, 26 Sep 2016 23:07:10 GMT
Hi,

Are 77, 78 and 79 three different entries? If so, ordering for them is not
defined in any case. They can potentially be stored on different nodes, and
therefore notifications can come from different nodes. In this case they can
arrive in any order, regardless of whether it's a listener notification or
initial query.

As for remote filters, Ignite automatically handles their deployment on new
nodes joining topology. The listener is lost only if the client that
deployed this listener fails or leaves.

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-avoid-the-event-lost-in-the-continuous-query-tp7904p7954.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Mime
View raw message