[
https://issues.apache.org/jira/browse/SENTRY-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16322583#comment-16322583
]
Na Li commented on SENTRY-2119:
-------------------------------
[~kkalyan] Is it possible for event_id to have permanent gap? If so, then there
is no way to know the event_id that is missing is temporary or permanent. If it
is temporary, we should get it with multiple retries. If it is permanent, we
should move on. However, there is no way to tell if the gap is permanent or
temporary.
> 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)
