sentry-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "kalyan kumar kalvagadda (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SENTRY-2109) Fix the logic of identifying HMS out of Sync
Date Thu, 04 Jan 2018 18:15:00 GMT

    [ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311782#comment-16311782
] 

kalyan kumar kalvagadda commented on SENTRY-2109:
-------------------------------------------------

[~lina.li] Purging is not an issue as we don't purge all the notifications. we keep latest
~100 entries while purging the table.

This patch addresses the scenario where Snapshot is triggered when there are gaps in between.
Yes, there could be some notifications that could be missed. This will not be addressed with
the patch.

> 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: SENTRY-2109.001.patch, SENTRY-2109.002.patch, SENTRY-2109.003.patch,
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)

Mime
View raw message