[
https://issues.apache.org/jira/browse/GEODE-9908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17476485#comment-17476485
]
ASF subversion and git services commented on GEODE-9908:
--------------------------------------------------------
Commit 109fdd88a41d21c53f8f3da3b1dff5677afab3d2 in geode's branch
refs/heads/develop from Jinmei Liao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=109fdd8 ]
GEODE-9908: when make durable client queue primary, send marker messa… (#7267)
> Marker message is delivered to the durable client after all the puts messages
> -----------------------------------------------------------------------------
>
> Key: GEODE-9908
> URL: https://issues.apache.org/jira/browse/GEODE-9908
> Project: Geode
> Issue Type: Bug
> Components: client queues
> Reporter: Jinmei Liao
> Assignee: Jinmei Liao
> Priority: Major
> Labels: pull-request-available
>
> When a durable client with registered interests, connects to the server:
> 1. it sends a readyForEvent message to the queue, the sever enqueues a marker
> message.
> 2. then the server enqueues all the puts messages to the queue.
> 3. the client disconnects (either by connection failure or by re-auth failure)
> 4. the client reconnects back to another server, the other server makes its
> queue primary, and enqueues another marker message.
> 5. if the first marker message hasn't been delivered to the client yet, the
> queue manager will delete the first marker message since marker messages
> should be conflated. Then all puts messages will be delivered before the
> marker message, thus the client won't put the values in its client cache.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
