[
https://issues.apache.org/jira/browse/HDDS-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyao Meng updated HDDS-2064:
-----------------------------
Description:
OM will NPE and crash when `ozone.om.service.ids=id1,id2` is configured but
`ozone.om.nodes.id1` doesn't exist; or `ozone.om.address.id1.omX` doesn't exist.
Root cause:
`OzoneManager#loadOMHAConfigs()` didn't check the case where `found == 0`. This
happens when local OM doesn't match any `ozone.om.address.idX.omX` in the
config.
was:
OM will NPE and crash when `ozone.om.service.ids=id1,id2` is configured but
`ozone.om.nodes.id1` doesn't exist.
Root cause:
`OzoneManager#loadOMHAConfigs()` didn't check the case where `found == 0`. This
happens when local OM doesn't match any `ozone.om.address.idX.omX` in the
config.
> OzoneManagerRatisServer#newOMRatisServer throws NPE when OM HA is configured
> incorrectly
> ----------------------------------------------------------------------------------------
>
> Key: HDDS-2064
> URL: https://issues.apache.org/jira/browse/HDDS-2064
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Siyao Meng
> Assignee: Siyao Meng
> Priority: Major
>
> OM will NPE and crash when `ozone.om.service.ids=id1,id2` is configured but
> `ozone.om.nodes.id1` doesn't exist; or `ozone.om.address.id1.omX` doesn't
> exist.
> Root cause:
> `OzoneManager#loadOMHAConfigs()` didn't check the case where `found == 0`.
> This happens when local OM doesn't match any `ozone.om.address.idX.omX` in
> the config.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
