You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@sentry.apache.org by "Na Li (JIRA)" <ji...@apache.org> on 2017/04/19 20:17:41 UTC

[jira] [Commented] (SENTRY-1669) HMSFollower should read current processed notification ID from database every time it runs

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

Na Li commented on SENTRY-1669:
-------------------------------

this issue can be fixed by changes in Sentry-1649 (to allow start()/stop() HMSFollower multiple times), which read current processed notification ID from database every time it runs

> 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
>            Reporter: Hao Hao
>            Assignee: kalyan kumar kalvagadda
>            Priority: Blocker
>             Fix For: sentry-ha-redesign
>
>
> 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)