Mike,
If you're using a CACHING_PROXY on the client region then concurrency
checks are enabled by default and tombstones will be created for the
region. This means the entry overhead is still in the cache.
If you disable concurrency checks like below, the tombstones won't be
created, and the entry overhead will be removed. But, then out-of-order
updates won't be prevented. I guess this would mainly be an issue with
register interest.
<region name="data" refid="CACHING_PROXY">
<region-attributes concurrency-checks-enabled="false">
<eviction-attributes>
<lru-entry-count maximum="1" action="local-destroy"/>
</eviction-attributes>
</region-attributes>
</region>
Thanks,
Barry Oglesby
On Fri, Aug 12, 2016 at 9:56 AM, Darrel Schneider <dschnei...@pivotal.io>
wrote:
> Destroy in general will get rid of both the entry, key, and value.
> Invalidate just gets rid of the value. But with the addition of tombstones
> destroy, initially, only gets rid of the value. The CachePerfStats have a
> stat "tombstones" that you can use even on a client to see how many
> entries+keys are currently in memory with no value because they have been
> destroyed but their tombstone has not yet been gc'd.
>
>
> On Fri, Aug 12, 2016 at 5:34 AM, Michael Stolz <mst...@pivotal.io> wrote:
>
>> In Geode Java client does LOCAL_DESTROY eviction action destroy the Entry
>> overhead as well as the payload?
>>
>> Also, are tombstones used on client cache?
>>
>> --
>> Mike Stolz
>> Principal Engineer, GemFire Product Manager
>> Mobile: 631-835-4771
>>
>
>
