[jira] [Created] (GEODE-1472) Setting Eviction destroy action on Patitioned Region could result in inconsistent data between redundant copies.

["Anilkumar Gingade (JIRA)" <ji...@apache.org>]

Anilkumar Gingade created GEODE-1472:
----------------------------------------

             Summary: Setting Eviction destroy action on Patitioned Region could result in inconsistent data between redundant copies.
                 Key: GEODE-1472
                 URL: https://issues.apache.org/jira/browse/GEODE-1472
             Project: Geode
          Issue Type: Bug
          Components: eviction
            Reporter: Anilkumar Gingade


The destroy eviction action on partitioned region is local operation; it  is not replicated between the redundant PR copies. This results in inconsistent data between the primary and secondary data copies. And will return inconsistent result with operation like get() and query, as these operation can fetch the data from either primary or secondary data, based on where they get initiated.
E.g. Client may have connected to both server1 (with bucket-1 primary) and server2 (with bucket-2 secondary), based on where the get/query operation routed, the client may see different result for a eviction-destroyed operation.
 
The implementation may have been done this way; with an assumption that, there will be a cache loader associated in this scenario, and the get will load evicted data (if not found) through cache loader...

This may not be true use-case as we are seeing Geode/GemFire is used as primary data store without data written/loaded from Cache loader...

To be consistent across the Region, Wan and AsyncQueue replication, the eviction destroy needs to be replicated across all the redundant nodes...








--
This message was sent by Atlassian JIRA
(v6.3.4#6332)