[
https://issues.apache.org/jira/browse/KNOX-2680?focusedWorklogId=716319&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-716319
]
ASF GitHub Bot logged work on KNOX-2680:
----------------------------------------
Author: ASF GitHub Bot
Created on: 27/Jan/22 10:03
Start Date: 27/Jan/22 10:03
Worklog Time Spent: 10m
Work Description: smolnar82 merged pull request #533:
URL: https://github.com/apache/knox/pull/533
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 716319)
Remaining Estimate: 0h
Time Spent: 10m
> Centralized Source of Cluster Configuration Details for Discovery
> -----------------------------------------------------------------
>
> Key: KNOX-2680
> URL: https://issues.apache.org/jira/browse/KNOX-2680
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Affects Versions: 1.5.0, 1.6.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Critical
> Fix For: 2.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, Knox performs cluster configuration discovery via the CM API for
> every descriptor (on start-up or descriptor/provider changed), even if the
> descriptors reference the same cluster. This discovery can be expensive and
> doing it multiple times only to get the same data yields sub-optimal
> performance.
> It will be better if Knox maintained a central record of the cluster
> configuration details, which could be referenced for every applicable
> descriptor, perhaps with some expiration of the validity of that record, such
> that multiple interactions with the CM API for the same cluster can be
> avoided. Not to mention, that Knox discovers all services found in the
> referenced cluster even if those services are not listed in any of the
> descriptors.
> The associated cluster configuration monitoring functionality will also need
> to be modified to accommodate this new behavior.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
