[
https://issues.apache.org/jira/browse/GEODE-9138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337622#comment-17337622
]
ASF subversion and git services commented on GEODE-9138:
--------------------------------------------------------
Commit d15601d16becbd483e0a66b86d78f8ab067736b8 in geode's branch
refs/heads/develop from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d15601d ]
GEODE-9138: Modified hasSeenEvent to log the message if necessary and and
increment a stat (#6362)
* There were 3 HA cases where the message was logged validly:
- posDup (for client message retries)
- low bucket redundancy (when a server crashes)
- recoveries in progress (when a server restarts)
* The first change was to convert the message from debug to info.
* These are all valid duplicates that we don't want to log if we can
help it. We really only want to log this message in steady-state (no HA).
* The first case was low bucket redundancy. In this case sometimes
posDup was true; sometimes not.
* Every message in this low bucket redundancy state should have been
posDup (they were all client retries). But posDup wasn't set on putAlls and
removeAlls. So, those changes and added the posDup case.
* The second case is that the region was being recovered. The messages
were logged for a specific bucket right after it was GII-ed, but the region was
still in recovery, so this is also ignored while logging.
Co-authored-by: Barry Oglesby <[email protected]>
Co-authored-by: Nabarun Nag <[email protected]>
> 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)
