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

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

                Author: ASF GitHub Bot
            Created on: 02/Jun/23 12:46
            Start Date: 02/Jun/23 12:46
    Worklog Time Spent: 10m 
      Work Description: smolnar82 merged PR #758:
URL: https://github.com/apache/knox/pull/758




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

    Worklog Id:     (was: 863504)
    Time Spent: 20m  (was: 10m)

> Ignore CORE_SETTINGS service discovery
> --------------------------------------
>
>                 Key: KNOX-2909
>                 URL: https://issues.apache.org/jira/browse/KNOX-2909
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: cm-discovery
>    Affects Versions: 2.1.0
>            Reporter: Sandor Molnar
>            Assignee: Sandor Molnar
>            Priority: Major
>             Fix For: 2.1.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> As a side-effect of KNOX-2899, Knox tries to scan the entire cluster (again) 
> during service discovery. In case CM is not reachable, but previous discovery 
> results are available in the service discovery repository (an in-memory 
> Caffeine cache), discovery fails, because it tries to get roles for a new CM 
> service called {{{}CORE-SETTINGS{}}}.
> This is a special CM service, which Knox's CM service discovery should 
> completely ignore.



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

Reply via email to