Hello,
It's come to my attention, when registering the cache event listener, the
filters get deployed on all the nodes of the cache, despite the fact that the
cache is configured as REPLICATED. This seems redundant since it's sufficient
to have the filter deployed only on the node that has the local cache listener
(in other words, the same node that registers the listener). Since the filter
may execute some non-trivial computationally intensive logic and it doesn't
make sense to waste CPU on the nodes that are not going to call back the
listener. Not deploying filters to remote nodes would also reduce the
registration/unregistration overhead since only the local node needs to be
involved.
The only case that would require special attention would be the case when a
listener is registered from a node which doesn't have the cache started.
Please advise.
Andrey
