[
https://issues.apache.org/jira/browse/GEODE-9138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337923#comment-17337923
]
Geode Integration commented on GEODE-9138:
------------------------------------------
Seen in [WindowsCoreIntegrationTestOpenJDK11
#177.1|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsCoreIntegrationTestOpenJDK11/builds/177.1]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0186/test-results/integrationTest/1619856193/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0186/test-artifacts/1619856193/windows-coreintegrationtestfiles-OpenJDK11-1.15.0-build.0186.tgz].
> 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)
