[
https://issues.apache.org/jira/browse/GEODE-9138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337840#comment-17337840
]
ASF subversion and git services commented on GEODE-9138:
--------------------------------------------------------
Commit 12cd50807dd71a22ad63e4e227e0540a1408e38e in geode's branch
refs/heads/feature/GEODE-9138-revert from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=12cd508 ]
Revert "GEODE-9138: Modified hasSeenEvent to log the message if necessary and
and increment a stat (#6362)"
This reverts commit d15601d16becbd483e0a66b86d78f8ab067736b8.
> 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
> Assignee: Barrett Oglesby
> 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)
