[
https://issues.apache.org/jira/browse/KNOX-2909?focusedWorklogId=863364&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-863364
]
ASF GitHub Bot logged work on KNOX-2909:
----------------------------------------
Author: ASF GitHub Bot
Created on: 02/Jun/23 07:12
Start Date: 02/Jun/23 07:12
Worklog Time Spent: 10m
Work Description: smolnar82 opened a new pull request, #758:
URL: https://github.com/apache/knox/pull/758
## What changes were proposed in this pull request?
The CORE_SETTINGS service in CM is a special one that does not need to be
discovered.
## How was this patch tested?
Unit testing and manual testing an a live CM cluster.
Issue Time Tracking
-------------------
Worklog Id: (was: 863364)
Remaining Estimate: 0h
Time Spent: 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: 10m
> 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)
