[ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301666#comment-16301666 ]
kalyan kumar kalvagadda commented on SENTRY-2109: ------------------------------------------------- Working on a patch to avoid the assumption mentioned above. New logic would make sure that the last notification processed by sentry is still in HMS_NOTIFICATION_LOG table to make sure that sentry is still in sync with HMS. > 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: 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)