devmadhuu opened a new pull request, #6752: URL: https://github.com/apache/ozone/pull/6752
## What changes were proposed in this pull request? This PR handles Recon startup failure due to unexpected runtime error and shuts down silently without logging the actual cause of error. Ozone Recon - Handle startup failure and log reasons as error due to SCM non-HA scenario While ReconServer.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. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-10937 ## How was this patch tested? Tested manually and added additional integration tests in Recon for non HA SCM case. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
