[HDDS-10702] Ozone Recon - Improve Recon startup failure handling and make it more resilient

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Labels: pull-request-available
• Assignee: Devesh Kumar Singh
• Reporter: Devesh Kumar Singh
• Created: 16/Apr/24 13:13
• Updated: 14/May/24 07:13
• Resolved: 14/May/24 07:13

Description

Recon can fail to start due to multiple reasons similar to other Ozone components, however Recon should recover from Runtime or unexpected failures during startup and provide a meaningful information on Recon UI :

• Related to failure of registering of datanodes and invalid network topology during Recon startup. When Recon starts up, it tries to loadExisting nodes and during loading of nodes, cluster topology get loaded which calls add of node during register of node event and if any discrepancy or invalid network topology, Recon startup fails.
• Related to initialization of pipelines.

Issue Links

• links to: GitHub Pull Request #6583