[
https://issues.apache.org/jira/browse/GEODE-9138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17333359#comment-17333359
]
ASF subversion and git services commented on GEODE-9138:
--------------------------------------------------------
Commit bdfa217667a9b8af6bef50ad602e3fb73e8ca7b7 in geode's branch
refs/heads/feature/GEODE-9138 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=bdfa217 ]
GEODE-9138: Modified hasSeenEvent to log the message if necessary and increment
a stat
> Add warning in server logs when data event is ignored as a duplicate
> --------------------------------------------------------------------
>
> Key: GEODE-9138
> URL: https://issues.apache.org/jira/browse/GEODE-9138
> Project: Geode
> Issue Type: Bug
> Components: client/server, logging
> Reporter: Diane Hardman
> Priority: Major
> Labels: pull-request-available
>
> Under certain rare conditions, a client may send or resend a data event with
> an eventId that causes the server to interpret it as a duplicate event and
> discard it.
> It is currently impossible to trace when this happens without extra logging
> added.
> From Barry:
> No, if the server thinks it has seen the event, it silently eats it. See
> DistributedEventTracker.hasSeenEvent. It has a trace log message but thats it.
> The log message that tracks this behavior in the server needs to be added
> permanently.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
