[jira] [Commented] (SENTRY-2109) Fix the logic of identifying HMS out of Sync

["Na Li (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16308834#comment-16308834 ] 

Na Li commented on SENTRY-2109:
-------------------------------

[~kkalyan] Sentry service periodically calls purgeNotificationIdTable. Have you take this into account in your update?

Since there is a gap and the Notification ID could decrease, the logic for getting notification events should be updated to too to make sure sentry gets all notifications. Otherwise, sentry may miss some notifications and will be inconsistent with HMS updates.

> Fix the logic of identifying HMS out of Sync
> --------------------------------------------
>
>                 Key: SENTRY-2109
>                 URL: https://issues.apache.org/jira/browse/SENTRY-2109
>             Project: Sentry
>          Issue Type: Bug
>          Components: Sentry
>    Affects Versions: 2.1.0
>            Reporter: kalyan kumar kalvagadda
>            Assignee: kalyan kumar kalvagadda
>             Fix For: 2.1.0
>
>         Attachments: SENTRY-2109.001.patch, SENTRY-2109.002.patch, SENTRY-2109.003.patch, Screenshot_HMS_NOTIFICATION_LOG.png
>
>
> Currently HMSFollower proactively checks if sentry is out of sync with HMS and initiates full snapshot, if needed.
> There will be false positives with the current logic if there are gaps in the event-id in the notification log sequence.
> This jira is aimed at making that logic robust.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)