[KNOX-2303] CM discovery - cluster config monitor should always perform initial config analysis after a delay

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 1.4.0
• Component/s: cm-discovery
• Assignee: Philip Zampino
• Reporter: Philip Zampino
• Created: 18/Mar/20 14:32
• Updated: 07/Apr/20 15:41
• Resolved: 07/Apr/20 15:41

Description

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.

Issue Links

• relates to: KNOX-2304 CM discovery - cluster config monitor needs to be aware of all relevant CM event types
• relates to: KNOX-2301 Trigger discovery for descriptors at gateway start time