[jira] [Updated] (KNOX-2994) Postpone CM configuration change monitoring until the Knox GW is up&running

["Sandor Molnar (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KNOX-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sandor Molnar updated KNOX-2994:
--------------------------------
    Status: Patch Available  (was: Open)

> Postpone CM configuration change monitoring until the Knox GW is up&running
> ---------------------------------------------------------------------------
>
>                 Key: KNOX-2994
>                 URL: https://issues.apache.org/jira/browse/KNOX-2994
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: cm-discovery, Server
>    Affects Versions: 1.6.0, 1.5.0, 2.0.0
>            Reporter: Sandor Molnar
>            Assignee: Sandor Molnar
>            Priority: Major
>             Fix For: 2.1.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> As of now, Knox starts CM configuration change monitoring right away it starts the {{{}DefaultClusterConfigurationMonitorService{}}}. This action will trigger the {{PollingConfigurationAnalyzer}} even when descriptors with possible service discovery settings are not even initialized.
> My suggestion is to take advantage of the recently introduced {{GatewayStatusService}} and set the {{isActive}} flag to true based on the result of {{{}org.apache.knox.gateway.services.topology.impl.GatewayStatusService.status(){}}}.



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