Cached data change notifications are used in multiple use-cases. Here is one -
We have OFFHEAP distributed Ignite cache fronted by JVM level local copy. It is similar to what Near cache would work. However, Ignite Near cache (JVM level local copy) also get serialized/de-serialized. which results in latency compared to direct object access. So we are not using Ignite Near cache but simulating same. To invalidate cache we rely on event notifications. In some case, we need to clear all cached entries and that is where we use cache.clear(). There are other scenarios where change event notifications are the preliminary indication of data change, which needs to be notified to all nodes to keep data and process consistency. Message passing can be another approach but it won't be completely consistent and tightly bound to data change. Can I assume cache.clear() does not generate any event notification and need to move away from it? Can you please help optimizing clear vs remove? Thanks, -Sam -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Event-Listeners-tp8306p14437.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
