sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dapeng Sun (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SENTRY-427) High availability for the SENTRY service
Date Mon, 27 Oct 2014 01:59:33 GMT

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

Dapeng Sun commented on SENTRY-427:
-----------------------------------

Hi folks
According Prasad's feedback in ReviewBoard, it's better to separate the jira into two jiras,
 one is 'Zookeeper' related, another is 'lock' related.

> High availability for the SENTRY service
> ----------------------------------------
>
>                 Key: SENTRY-427
>                 URL: https://issues.apache.org/jira/browse/SENTRY-427
>             Project: Sentry
>          Issue Type: New Feature
>            Reporter: Dapeng Sun
>            Assignee: Dapeng Sun
>         Attachments: SENTRY-427.patch, SENTRY-427.patch, SENTRY_HA_Design.pdf
>
>
> The HA(High availability) feature contains four parts
> * SENTRY service discovery:The sentry service should be registered to Zookeeper cluster,
and client can get the active node from Zookeeper, then connect to the node.
> * SENTRY Sequence Id: There should be a distribute counter(zookeeper) to make sure the
increment of sequence id. 
> * Transaction:Transaction should be supported in distributed environment.
> * Security(Kerberos) support



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message