[
https://issues.apache.org/jira/browse/GEODE-7663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu updated GEODE-7663:
----------------------------
Labels: GeodeCommons (was: )
> Delta updates can be lost in client cache proxy due to asynchronous nature of
> HARegionQueue
> -------------------------------------------------------------------------------------------
>
> Key: GEODE-7663
> URL: https://issues.apache.org/jira/browse/GEODE-7663
> Project: Geode
> Issue Type: Bug
> Components: client queues
> Reporter: Eric Shu
> Priority: Major
> Labels: GeodeCommons
>
> This was found when trying to add test coverage for Tomcat Server
> (GEODE-7109).
> Assume client1 (cache proxy) creates session (from tomcat server1) and
> updates attributes a few times. These delta updates will be send to Geode
> servers. For each update, server will generate a new version and will queue
> these delta updates to send to other client caches.
> Assume that there is a fail over case and the session fail over to tomcat
> server2 (with geode client 2 cache proxy cache). The newer update on the
> session on client 2 will be sent to servers. Once the update is successful on
> the server, it will be applied to client 2 local cache (with a newest version
> for the key). Now this cache operation will block the earlier updates sent
> through HARegionQueue from server to client 2. This will lead to attributes
> (delta updates) are lost on client 2 local cache -- causing the data
> inconsistency.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
