[ 
https://issues.apache.org/jira/browse/KNOX-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sandor Molnar reassigned KNOX-3027:
-----------------------------------

    Assignee: Sandeep More  (was: Sandor Molnar)

> CM discovery cache improvements
> -------------------------------
>
>                 Key: KNOX-3027
>                 URL: https://issues.apache.org/jira/browse/KNOX-3027
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: cm-discovery, Server
>    Affects Versions: 2.0.0, 1.6.0
>            Reporter: Sandor Molnar
>            Assignee: Sandeep More
>            Priority: Critical
>             Fix For: 2.1.0
>
>
> With KNOX-2680 in place, Knox maintains an in-memory cache that stores CM 
> service discovery data. This repository was a huge improvement and solved 
> some of the performance issues around CM service discovery, but there are 
> some drawback:
>  * administrators are required to fine-tune the cache entry TTL as the 
> default 10 minutes can be low in many cases
>  * the repository does not survive Knox restarts
> I propose to implement the following changes:
>  * entries in that repository shall not be invalidated. They would live in 
> memory throughout the entire lifetime of the Knox Gateway. The existing 
> PollingConfigAnalyzer logic must be updated to keep that repository in synch.
>  * the repository should be serialized in the DATA_DIR during the shutdown of 
> the Knox Gateway. It should also be populated from the previously persisted 
> data at startup time. If there was a change on the cluster when Knox was 
> down, PollingConfigurationAnalyzer will eventually sync the repository.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to