[ 
https://issues.apache.org/jira/browse/HDDS-2064?focusedWorklogId=305834&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-305834
 ]

ASF GitHub Bot logged work on HDDS-2064:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 03/Sep/19 19:58
            Start Date: 03/Sep/19 19:58
    Worklog Time Spent: 10m 
      Work Description: smengcl commented on pull request #1398: [WIP] 
HDDS-2064. OzoneManagerRatisServer#newOMRatisServer throws NPE when OM HA is 
configured incorrectly
URL: https://github.com/apache/hadoop/pull/1398
 
 
   The WIP patch can prevent NPE in `TestOzoneManagerConfiguration` unit test 
`testWrongConfigurationNoOMNodes` and `testWrongConfigurationNoOMAddrs`. But it 
fails `testWrongConfiguration` and `testMultipleOMServiceIds`.
   
   I might need to place the fix logic in other places instead of 
`OzoneManager` to pass the other unit tests without modifying them? Please 
advice.
 
----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

            Worklog Id:     (was: 305834)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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]

Reply via email to