Due to the particulars of eviction in GemFire, when eviction is configured with the local-destroy action each member hosting the partitioned region performs the local-destroy independently and without synchronization. As a result, CQ clients may receive varying events depending on which member those clients are connected to.
As an example, consider the following example:
In this situation, a CQ event is sent to ClientA because the entry still existed on the primary when the destroy region operation was invoked. On the other hand, the CQ event is not sent to ClientB because the entry had already been evicted on the secondary, MemberB.
Environment
All versions of the GemFire which include Partitioned Regions, Continuous Query, and Eviction.