You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/02/24 17:03:00 UTC
[jira] [Commented] (KNOX-2680) Centralized Source of Cluster Configuration Details for Discovery
[ https://issues.apache.org/jira/browse/KNOX-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497557#comment-17497557 ]
ASF subversion and git services commented on KNOX-2680:
-------------------------------------------------------
Commit a29223a58c96947bfa8e4d61bc0f9d558198bfe1 in knox's branch refs/heads/webshell from Sandor Molnar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=a29223a ]
KNOX-2680 - Introducing a central repository for CM service discovery configs (#533)
* KNOX-2680 - Filtering CM service discovery by service names listed in the given topology
* KNOX-2680 - Introducing a central repository for CM service discovery configs
> 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)