[jira] [Work logged] (KNOX-2899) Disable service-based discovery

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

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

                Author: ASF GitHub Bot
            Created on: 18/Apr/23 08:54
            Start Date: 18/Apr/23 08:54
    Worklog Time Spent: 10m 
      Work Description: smolnar82 opened a new pull request, #749:
URL: https://github.com/apache/knox/pull/749

   ## What changes were proposed in this pull request?
   
   Service-based filtering is temporarily disabled while discovering a CM cluster.
   
   ## How was this patch tested?
   
   Manually tested using a large CM cluster with lots of services.
   




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

            Worklog Id:     (was: 857585)
    Remaining Estimate: 0h
            Time Spent: 10m

> Disable service-based discovery
> -------------------------------
>
>                 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: 10m
>  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)