[
https://issues.apache.org/jira/browse/SENTRY-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005534#comment-16005534
]
Sergio Peña commented on SENTRY-1760:
-------------------------------------
So, there are a few cases that will require a full snapshot:
- sentry is down for a while
- errros while processing notifications
- HDFS sync is disabled
- HMS DB is reset. I don't know how we would be able to detect if the HMS
notification DB is reset. Perhaps the current HMS notification ID will be less
than the already processed ID on Sentry, and if so a full snapshot is required?
I don't trust on this, though.
However, if there are different scenarios causing a gap, can we just force a
full snapshot on every Sentry restart?
> HMSFollower should detect when a full snapshot from HMS is required
> -------------------------------------------------------------------
>
> Key: SENTRY-1760
> URL: https://issues.apache.org/jira/browse/SENTRY-1760
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
> Affects Versions: sentry-ha-redesign
> Reporter: Alexander Kolbasov
> Assignee: Sergio Peña
> Priority: Blocker
> Fix For: sentry-ha-redesign
>
>
> The current criteria for getting a full snapshot from HMS is insufficient. We
> need to get full snapshot every time when there is a gap between last stored
> notification and the smallest notification available from HMS.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
