[
https://issues.apache.org/jira/browse/SENTRY-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16302224#comment-16302224
]
Hadoop QA commented on SENTRY-2106:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12903475/SENTRY-2106.01.patch
against master.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} all tests passed
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/3592/console
This message is automatically generated.
> Sentry ahead full snapshot retry logic
> --------------------------------------
>
> 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
> Labels: features
> Fix For: 2.1.0
>
> Attachments: SENTRY-2106.01.patch
>
>
> Once SentryHMSNotification table is not empty, there are two cases when a
> full snapshot is triggered.
> # If first event in list of notifications received from HMS greater than
> latest sentry hms notification Id
> # If latest sentry notification Id is greater than current hms notification Id
> The later is a unexpected case where for some reason sentry gets ahead of
> HMS. We should add a logic to trigger a full snapshot in case 2 only after a
> configurable number of retries. This will avoid unnecessary full snapshot
> triggers as they are resource intensive
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
