You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2017/02/17 21:52:44 UTC

[jira] [Commented] (SENTRY-1448) Store processed notification sequence ID in database

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

Hadoop QA commented on SENTRY-1448:
-----------------------------------

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12853318/SENTRY-1448.001-sentry-ha-redesign.patch against sentry-ha-redesign.

{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/2354/console

This message is automatically generated.

> Store processed notification sequence ID in database
> ----------------------------------------------------
>
>                 Key: SENTRY-1448
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1448
>             Project: Sentry
>          Issue Type: Sub-task
>          Components: Sentry
>    Affects Versions: sentry-ha-redesign
>            Reporter: Alexander Kolbasov
>            Assignee: Hao Hao
>             Fix For: sentry-ha-redesign
>
>         Attachments: SENTRY-1448.001-sentry-ha-redesign.patch
>
>
> In order to implement correct failover in Sentry HA sentry needs to keep the latest processed notification sequence ID from the notification log in a persistent storage. Otherwise the new master doesn't know what events were processed and what were not.
> To do it, we need to add the notification id in path delta update table,  to identify for each delta path update, its corresponding notification event.  Thus, the latest processed notification sequence ID is stored with the latest path update table.



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