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 2023/04/20 18:02:00 UTC

[jira] [Commented] (KNOX-2899) Disable service-based discovery filter

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

ASF subversion and git services commented on KNOX-2899:
-------------------------------------------------------

Commit 45394aa590af4b14a874ec49340e450dd20611d9 in knox's branch refs/heads/master from Sandor Molnar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=45394aa59 ]

KNOX-2899 - Disable service-based discovery filter in Cloudera Manager service discovery (#749)



> Disable service-based discovery filter
> --------------------------------------
>
>                 Key: KNOX-2899
>                 URL: https://issues.apache.org/jira/browse/KNOX-2899
>             Project: Apache Knox
>          Issue Type: Task
>          Components: Server
>            Reporter: Sandor Molnar
>            Assignee: Sandor Molnar
>            Priority: Major
>             Fix For: 2.1.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> With KNOX-2680, the Knox team introduced two major changes in Cloudera Manager service discovery:
>  * the first is that Knox only discovers services that are actually listed in the given descriptor (instead of discovering the entire cluster)
>  * from now on, Knox maintains an in-memory repository of discovered data (cluster, service, and role configs). Caffeine is used as the cache implementation with the default of 10 mins of cache entry TTL.
> It turns out the first improvement may cause redundant topology redeployments due to "missing" service discovery details while the {{Polling Configuration Analyzer}} finds a relevant event that belongs to a service that was not included in the latest discovery round.
> For now, we should disable that feature temporarily until it's clear how to enable and address the redundant redeployment issue.



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