[ https://issues.apache.org/jira/browse/SENTRY-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16317338#comment-16317338 ]
kalyan kumar kalvagadda commented on SENTRY-2119: ------------------------------------------------- *Approach-2:* As we process the notifications we HMSFollower would know if there are any notifications that are missed. We need to record/persist them . # We need to have configured interval to schedule a retry of missed notifications. # when the missed event-ids are persisted we need to persist the current time stamp as well # we need to have a time interval to purge this data. # When the event-id are purged we unblock any HMS threads if needed. > HMSFollower may not fetch HMS notifications which are out of order > ------------------------------------------------------------------ > > Key: SENTRY-2119 > URL: https://issues.apache.org/jira/browse/SENTRY-2119 > Project: Sentry > Issue Type: Bug > Components: Sentry > Affects Versions: 2.1.0 > Reporter: kalyan kumar kalvagadda > Assignee: kalyan kumar kalvagadda > > With the current implementation of HMS and HMS-HA notifications inserted in > NOTIFICATION_LOG table can be out of order. That means, notifications with > smaller event-id's can be inserted into the table later and there is not > clear understanding on on the time difference between them. > When this happens HMSFollower will not be able to fetch these notifications. -- This message was sent by Atlassian JIRA (v6.4.14#64029)