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

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.0, 2.0.0, 1.6.0
• Fix Version/s: 2.1.0
• Component/s: cm-discovery, Server
• Assignee: Sandor Molnar
• Reporter: Sandor Molnar
• Created: 12/Dec/23 09:14
• Updated: 27/Feb/24 09:22
• Resolved: 04/Jan/24 07:32

Description

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().

Issue Links

• links to: GitHub Pull Request #831