Cache loaders should only be invoked if you do a "get" operation. In this case you are just registering interest which is not a "get" operation. With register interest you are saying "if this key every exists let me know" and doing that should not cause it to exist.
On Fri, Feb 24, 2017 at 4:21 PM, Michael Stolz <mst...@pivotal.io> wrote: > Seems to me this is correct behavior. If you registered a cache loader you > want it to work > > -- > Mike Stolz > Principal Engineer - Gemfire Product Manager > Mobile: 631-835-4771 > > On Feb 24, 2017 5:59 PM, "Barry Oglesby (JIRA)" <j...@apache.org> wrote: > > > > > [ https://issues.apache.org/jira/browse/GEODE-2547?page= > > com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > > > > Barry Oglesby reassigned GEODE-2547: > > ------------------------------------ > > > > Assignee: Barry Oglesby > > > > > Interest registration can cause a CacheLoader to be invoked > > > ----------------------------------------------------------- > > > > > > Key: GEODE-2547 > > > URL: https://issues.apache.org/jira/browse/GEODE-2547 > > > Project: Geode > > > Issue Type: Bug > > > Components: client queues > > > Reporter: Barry Oglesby > > > Assignee: Barry Oglesby > > > > > > A simple scenario to reproduce this issue is: > > > - configure a Region with a CacheLoader > > > - destroy a key (it doesn't matter if the entry exists) > > > - register interest in that key > > > The CacheLoader will be invoked > > > > > > > > -- > > This message was sent by Atlassian JIRA > > (v6.3.15#6346) > > >
