Hi all,
we're faced with the following requirement - when a cache entry expires
and is about to get removed from the cache, listen to the event, alter an
attribute on the entry and write it to some other cache.
It can be implemented as a client-side event listener, but that ceases to
function as soon as the client leave the topology.
/ UUID listenerId = ignite.events().remoteListen(
(e, uuid) -> {
System.out.println("Expired event - executed on the
client");
return true;
},
e -> {
System.out.println("Expired event - executed on one of the
servers");
return true;
},
EventType.EVT_CACHE_OBJECT_EXPIRED
);/
Calling /ignite.events(ignite.cluster().forServers()).remoteListen / instead
makes no difference as long as I can tell.
Is there any way to run an event listener on the server without a
corresponding client? Is there any way for the listener to outlive its
client?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
