[
https://issues.apache.org/jira/browse/KNOX-2284?focusedWorklogId=400905&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-400905
]
ASF GitHub Bot logged work on KNOX-2284:
----------------------------------------
Author: ASF GitHub Bot
Created on: 10/Mar/20 18:15
Start Date: 10/Mar/20 18:15
Worklog Time Spent: 10m
Work Description: smolnar82 commented on pull request #285: KNOX-2284 -
Handling CM descriptors after Knox shared-provider/descriptor/topology monitors
are started
URL: https://github.com/apache/knox/pull/285
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 400905)
Time Spent: 20m (was: 10m)
> CM descriptors do not get picked up at Gateway start
> ----------------------------------------------------
>
> Key: KNOX-2284
> URL: https://issues.apache.org/jira/browse/KNOX-2284
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 1.4.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Major
> Fix For: 1.4.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When there is a CM descriptor in the KNOX_DESCRIPTORS_DIR at startup time and
> the KNOX descriptors found in this CM descriptor did not exist before then
> Knox does not pick up them.
> The reason is: the shared-provider/descriptor/topology monitor starts after
> the CM descriptor is being parsed and the Knox descriptors are persisted.
> Recommended solution: move the CM descriptor handling after the monitors are
> started.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
