You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sentry.apache.org by "guoquan (JIRA)" <ji...@apache.org> on 2015/03/18 06:22:45 UTC
[jira] [Updated] (SENTRY-464) Sentry service register and using
InvocationHandler for SentryPolicyServiceClientFactory high availability
[ https://issues.apache.org/jira/browse/SENTRY-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
guoquan updated SENTRY-464:
---------------------------
Fix Version/s: 1.5.0
> Sentry service register and using InvocationHandler for SentryPolicyServiceClientFactory high availability
> ----------------------------------------------------------------------------------------------------------
>
> Key: SENTRY-464
> URL: https://issues.apache.org/jira/browse/SENTRY-464
> Project: Sentry
> Issue Type: Sub-task
> Reporter: Dapeng Sun
> Assignee: Dapeng Sun
> Fix For: 1.5.0
>
> Attachments: SENTRY-464-002.patch, SENTRY-464.003.patch, SENTRY-464.004.patch, SENTRY-464.005.patch, SENTRY-464.patch
>
>
> * Add service register in SentryPolicyStoreProcessor
> * Add HASentryPolicyServiceClientImpl as a HA implementation for SentryPolicyServiceClient, it can select active node which registered in Zookeeper
> * Add InvocationHandler, use SentryPolicyServiceClientDefaultImpl as a field, this make all HA method can reuse the same logic for retry.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)