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 2020/03/10 18:17:00 UTC
[jira] [Commented] (KNOX-2284) CM descriptors do not get picked up
at Gateway start
[ https://issues.apache.org/jira/browse/KNOX-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17056215#comment-17056215 ]
ASF subversion and git services commented on KNOX-2284:
-------------------------------------------------------
Commit 6ca3a4eab9ccb83f17dd8efebf7b8c499aa244f2 in knox's branch refs/heads/master from Sandor Molnar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=6ca3a4e ]
KNOX-2284 - Handling CM descriptors after Knox shared-provider/descriptor/topology monitors are started (#285)
> 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)