chiraggoyal19 opened a new pull request, #9282:
URL: https://github.com/apache/ozone/pull/9282

   ## What changes were proposed in this pull request?
   This PR improves error messages when SCM bootstrap fails due to 
configuration typos.
   Currently, misspelling ozone.scm.service.ids as ozone.scm.service.id causes 
a generic "Failed to get SCM info" error with the root cause buried in stack 
traces.
   Changes:
   Added proactive check in SCMNodeInfo.buildNodeInfo() to detect the common 
typo immediately
   Enhanced exception handling in HAUtils, StorageContainerManagerStarter, and 
SCMFailoverProxyProviderBase to provide clear error messages listing which 
properties to verify
   Result: Operators now see specific error messages pointing directly to 
configuration problems.
   
   ## What is the link to the Apache JIRA
   https://issues.apache.org/jira/browse/HDDS-13886
   
   ## How was this patch tested?
   Modified the ozone.scm.service.ids property in the Docker configuration file 
to reflect the updated configuration.
   Executed the ozone scm --bootstrap command to validate the changes.
   The command completed successfully, and SCM initialization logs confirmed 
the correct application of the updated configuration.
   
   ```
   2025-11-11 18:59:13,009 [main] ERROR server.StorageContainerManagerStarter: 
SCM bootstrap failed. Failed to get SCM info due to configuration error.
   Please verify SCM HA configuration properties:
     - ozone.scm.service.ids
     - ozone.scm.nodes.<serviceId>
     - ozone.scm.address.<serviceId>.<nodeId>
   Common issues: missing service IDs, incorrect hostnames, or missing port 
numbers.
   Details: Configuration property 'ozone.scm.service.ids' is missing.
   For SCM HA configuration, use 'ozone.scm.service.ids' to specify service IDs.
   2025-11-11 18:59:13,009 [main] ERROR server.StorageContainerManagerStarter: 
Root cause: Configuration property 'ozone.scm.service.ids' is missing.
   For SCM HA configuration, use 'ozone.scm.service.ids' to specify service IDs.
   Failed to get SCM info due to configuration error.
   2025-11-11 18:59:13,012 [shutdown-hook-0] INFO 
server.StorageContainerManagerStarter: SHUTDOWN_MSG: 
   /************************************************************
   SHUTDOWN_MSG: Shutting down StorageContainerManager at 
12223274cf5e/172.18.0.6
   ************************************************************/
   sh-5.1$ 
   
   ```


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

Reply via email to