[
https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001814#comment-16001814
]
kalyan kumar kalvagadda edited comment on SENTRY-1669 at 5/9/17 12:00 AM:
--------------------------------------------------------------------------
HMSFollower is the only thread that updates the notification ID . Do we need to
consider that case for any reason?
This case is possible when HMSFollower is running in both the instances.
was (Author: kkalyan):
HMSFollower is the only thread that updates the notification ID . Do we need to
consider that case for any reason?
> HMSFollower should read current processed notification ID from database every
> time it runs
> ------------------------------------------------------------------------------------------
>
> Key: SENTRY-1669
> URL: https://issues.apache.org/jira/browse/SENTRY-1669
> Project: Sentry
> Issue Type: Sub-task
> Components: Hdfs Plugin
> Affects Versions: sentry-ha-redesign
> Reporter: Hao Hao
> Assignee: kalyan kumar kalvagadda
> Priority: Blocker
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1669.001-sentry-ha-redesign.patch
>
>
> Instead of using in-memory current processed notification ID, HMSFollower
> should read the processed notification ID info from database every time it
> runs. Otherwise, after failover, the new leader cannot get the correct
> up-to-date processed notification ID.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
