[
https://issues.apache.org/jira/browse/SENTRY-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16317254#comment-16317254
]
kalyan kumar kalvagadda edited comment on SENTRY-2119 at 1/8/18 11:30 PM:
--------------------------------------------------------------------------
*Approach-1:* When ever HMSFollower fetches notifications from HMS it can go
back by configurable number of event-id's and fetch the notifications. That
way, if there are any notifications that were missed in the previous fetch
requests they can be fetched and processed later.
This solution is not fool proof. Going back "N" event-id's and fetching older
notifications may not solve the issue in all the cases but it can minimize the
chase of it.
was (Author: kkalyan):
*Solution Approach:* When ever HMSFollower fetches notifications from HMS it
can go back by configurable number of event-id's and fetch the notifications.
That way, if there are any notifications that were missed in the previous fetch
requests they can be fetched and processed later.
This solution is not fool proof. Going back "N" event-id's and fetching older
notifications may not solve the issue in all the cases but it can minimize the
chase of it.
> 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)
