[jira] [Commented] (KNOX-2134) Add caching to ZookeeperRemoteAliasService

["Kevin Risden (Jira)" <ji...@apache.org>]

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

Kevin Risden commented on KNOX-2134:
------------------------------------

Curator doesn't handle this today? Seems like something we shouldn't have to maintain our own cache for if possible. Would be nice to say hey curator for this path I want to query it and it be up to date.

> Add caching to ZookeeperRemoteAliasService
> ------------------------------------------
>
>                 Key: KNOX-2134
>                 URL: https://issues.apache.org/jira/browse/KNOX-2134
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 1.3.0
>            Reporter: Philip Zampino
>            Assignee: Philip Zampino
>            Priority: Major
>             Fix For: 1.4.0
>
>
> The ZookeeperRemoteAliasService implementation always goes to ZooKeeper to retrieve alias data. Instead, it should cache the data locally to make password retrieval much faster.
> The implementation already receives pushes from ZooKeeper when alias znodes change, so instead of only updating the associated local alias service, it can also update its own cache.
> This way, it only ever needs to go to ZooKeeper for add/remove operations.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)