[ 
https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

kalyan kumar kalvagadda updated SENTRY-1669:
--------------------------------------------
    Attachment: SENTRY-1669.008-sentry-ha-redesign.patch

Updating the rebased patch.

> 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, 
> SENTRY-1669.002-sentry-ha-redesign.patch, 
> SENTRY-1669.003-sentry-ha-redesign.patch, 
> SENTRY-1669.004-sentry-ha-redesign.patch, 
> SENTRY-1669.005-sentry-ha-redesign.patch, 
> SENTRY-1669.006-sentry-ha-redesign.patch, 
> SENTRY-1669.007-sentry-ha-redesign.patch, 
> SENTRY-1669.008-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.
> It should also update the Notification ID to database once it processes a 
> notification event. The Notification ID in database should keep on increase 
> (we don't handle its overflow scenario).
> notification id is also available in SENTRY_PATH_CHANGE table but it is not 
> dependable to get the last notification processed. Sentry server can not 
> depend on this information to get the last notification that the server 
> processed as it not guaranteed that every notification will make it to 
> SENTRY_PATH_CHANGE. Under various conditions notifications will not make it 
> to SENTRY_PATH_CHANGE table so we need separate table to store the ID's.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to