[
https://issues.apache.org/jira/browse/SENTRY-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16339517#comment-16339517
]
Alexander Kolbasov commented on SENTRY-2106:
--------------------------------------------
As mentioned in SENTRY-2109, it is better to fix the root cause on the HMS side.
> Remove sentry dependency on HMS table NOTIFICATION_SEQUENCE when checking if
> Sentry is out-of-sync with HMS
> -----------------------------------------------------------------------------------------------------------
>
> Key: SENTRY-2106
> URL: https://issues.apache.org/jira/browse/SENTRY-2106
> Project: Sentry
> Issue Type: New Feature
> Components: Sentry
> Affects Versions: 2.1.0
> Reporter: Arjun Mishra
> Assignee: Arjun Mishra
> Priority: Major
> Labels: features
> Fix For: 2.1.0
>
> Attachments: SENTRY-2106.01.patch, SENTRY-2106.02.patch,
> SENTRY-2106.03.patch, SENTRY-2106.04.patch, SENTRY-2106.05.patch,
> SENTRY-2106.06.patch
>
>
> After steady state, a full snapshot is triggered by mainly 2 cases
> # Sentry is "ahead"
> # Sentry is behind
> Case 1 has a dependency on NOTIFICATION_SEQUENCE table. This is not reliable
> as it was observed that sometimes NOTIFICATION_SEQUENCE and NOTIFICATION_LOG
> are not in sync. As a result of this unnecessary full snapshots can be
> triggered.
> The fix is to remove this dependency
>
> PLEASE NOTE THAT THIS SHOULD BE COMMITTED WITH SENTRY-2109
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
