You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Philip Zampino (Jira)" <ji...@apache.org> on 2020/04/07 15:42:00 UTC
[jira] [Commented] (KNOX-2303) CM discovery - cluster config
monitor should always perform initial config analysis after a delay
[ https://issues.apache.org/jira/browse/KNOX-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077351#comment-17077351 ]
Philip Zampino commented on KNOX-2303:
--------------------------------------
With KNOX-2301 and KNOX-2304, this should no longer be necessary.
> CM discovery - cluster config monitor should always perform initial config analysis after a delay
> -------------------------------------------------------------------------------------------------
>
> Key: KNOX-2303
> URL: https://issues.apache.org/jira/browse/KNOX-2303
> Project: Apache Knox
> Issue Type: Improvement
> Components: cm-discovery
> Affects Versions: 1.4.0
> Reporter: Philip Zampino
> Assignee: Philip Zampino
> Priority: Major
>
> The CM cluster configuration monitor should have a configurable initial delay, after which it will begin polling for cluster changes.
> The first pass of the monitor for a given source and cluster should analyze the configuration regardless of restart events, such that it will discover changes that have been effected without any service restarts.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)