Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
0.4.1
-
None
Description
Testing for the OM HA feature, I update the HA specific configurations and then start up the OM service. But I find OM is not startup succeed and I check the log, I get this error info and no any other helpful message.
... 2020-01-17 08:57:55,210 [main] INFO - registered UNIX signal handlers for [TERM, HUP, INT] 2020-01-17 08:57:55,846 [main] INFO - ozone.om.internal.service.id is not defined, falling back to ozone.om.service.ids to find serviceID for OzoneManager if it is HA enabled cluster 2020-01-17 08:57:55,872 [main] INFO - Found matching OM address with OMServiceId: om-service-test, OMNodeId: omNode-1, RPC Address: lyq-m1-xx.xx.xx.xx:9862 and Ratis port: 9872 2020-01-17 08:57:55,872 [main] INFO - Setting configuration key ozone.om.http-address with value of key ozone.om.http-address.omNode-1: lyq-m1-xx.xx.xx.xx:9874 2020-01-17 08:57:55,872 [main] INFO - Setting configuration key ozone.om.https-address with value of key ozone.om.https-address.omNode-1: lyq-m1-xx.xx.xx.xx:9875 2020-01-17 08:57:55,872 [main] INFO - Setting configuration key ozone.om.address with value of key ozone.om.address.omNode-1: lyq-m1-xx.xx.xx.xx:9862 OM not initialized. 2020-01-17 08:57:55,887 [shutdown-hook-0] INFO - SHUTDOWN_MSG:
"OM not initialized" doesn't give me enough info, then I have to check the related logic code. Finally, I find I have made a mistake that I forgot to do the om --init command first before startup the OM.
We can additionally add with suggestion here that will help users quickly know the error and how to resolved that.
Attachments
Issue Links
- links to