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

ASF GitHub Bot logged work on KNOX-2134:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Dec/19 07:51
            Start Date: 18/Dec/19 07:51
    Worklog Time Spent: 10m 
      Work Description: smolnar82 commented on pull request #218: KNOX-2134 - 
Checking if password is available via local alias service before going to fetch 
it from remote ZK server
URL: https://github.com/apache/knox/pull/218
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 361326)
    Time Spent: 2h 40m  (was: 2.5h)

> 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: Sandor Molnar
>            Priority: Major
>             Fix For: 1.4.0
>
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> 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)

Reply via email to