Bruce Schuchardt created GEODE-5596:
---------------------------------------
Summary: Client ends up with destroyed entry after invalidate()
Key: GEODE-5596
URL: https://issues.apache.org/jira/browse/GEODE-5596
Project: Geode
Issue Type: Improvement
Components: regions
Reporter: Bruce Schuchardt
If a client is doing a destroy, putAll and invalidate in separate threads and
the events align like this in the server: destroy then create then invalidate,
the client may end up having a destroyed entry instead of an invalid entry.
This is a long standing issue with Geode (and formerly with GemFire) that a
client does not create an Invalid entry in some situations. A lot of this was
cleared up when we implemented concurrency controls in the cache but this one
corner case remains.
Fixing this issue requires a small change in behavior for client caches in how
they handle the invalidate() operation, but I think it's a change for the
better.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
