You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Sumit Agrawal (Jira)" <ji...@apache.org> on 2024/05/14 07:14:00 UTC
[jira] [Resolved] (HDDS-10702) Ozone Recon - Improve Recon startup failure handling and make it more resilient
[ https://issues.apache.org/jira/browse/HDDS-10702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sumit Agrawal resolved HDDS-10702.
----------------------------------
Fix Version/s: 1.5.0
Resolution: Fixed
> Ozone Recon - Improve Recon startup failure handling and make it more resilient
> -------------------------------------------------------------------------------
>
> Key: HDDS-10702
> URL: https://issues.apache.org/jira/browse/HDDS-10702
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Devesh Kumar Singh
> Assignee: Devesh Kumar Singh
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org