You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "kalyan kumar kalvagadda (JIRA)" <ji...@apache.org> on 2018/01/08 22:39:00 UTC
[jira] [Commented] (SENTRY-2119) HMSFollower may not fetch HMS
notifications which are out of order
[ https://issues.apache.org/jira/browse/SENTRY-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16317255#comment-16317255 ]
kalyan kumar kalvagadda commented on SENTRY-2119:
-------------------------------------------------
[~vspector@gmail.com] FYI
> 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)