You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/05/30 14:55:00 UTC

[jira] [Updated] (HDDS-10937) Ozone Recon - Handle startup failure and log reasons as error due to SCM non-HA scenario

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

ASF GitHub Bot updated HDDS-10937:
----------------------------------
    Labels: pull-request-available  (was: )

> Ozone Recon - Handle startup failure and log reasons as error due to SCM non-HA scenario
> ----------------------------------------------------------------------------------------
>
>                 Key: HDDS-10937
>                 URL: https://issues.apache.org/jira/browse/HDDS-10937
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: Ozone Recon
>            Reporter: Devesh Kumar Singh
>            Assignee: Devesh Kumar Singh
>            Priority: Major
>              Labels: pull-request-available
>
> Ozone Recon - Handle startup failure and log reasons as error due to SCM non-HA scenario
>  # While Recon.start() method is called, if any runtime errors being thrown, those are not being logged and Recon startup fails silently without logging any reason of failure. E.g. In case of non-HA SCM case, few configurations made Recon fails to start. This scenario or any runtime exception  needs to be handled for proper logging.
>  # In non-HA SCM case, while trying to fetch SCM DB snapshot, SCM peer roles are not being returned correctly, so the logic needs to handle.



--
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