hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (HDDS-1355) Only FQDN is accepted for OM rpc address in secure environment
Date Tue, 02 Apr 2019 00:21:00 GMT

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

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

                Author: ASF GitHub Bot
            Created on: 02/Apr/19 00:20
            Start Date: 02/Apr/19 00:20
    Worklog Time Spent: 10m 
      Work Description: ajayydv commented on pull request #677: HDDS-1355. Only FQDN is accepted
for OM rpc address in secure environment. Contributed by Ajay Kumar.
URL: https://github.com/apache/hadoop/pull/677
 
 
   
 
----------------------------------------------------------------
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:
users@infra.apache.org


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

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

> Only FQDN is accepted for OM rpc address in secure environment
> --------------------------------------------------------------
>
>                 Key: HDDS-1355
>                 URL: https://issues.apache.org/jira/browse/HDDS-1355
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Elek, Marton
>            Assignee: Ajay Kumar
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> While the scm address can be a host name (relative to the current search domain) if the
om address is just a hostname and not a FQDN a NPE is thrown:
> {code}
>   10   │   OZONE-SITE.XML_ozone.om.address: "om-0.om"
>   11   │   OZONE-SITE.XML_ozone.scm.client.address: "scm-0.scm"
>   12   │   OZONE-SITE.XML_ozone.scm.names: "scm-0.scm"
> {code} 
> {code}
> 2019-03-29 14:37:52 ERROR OzoneManager:865 - Failed to start the OzoneManager.
> java.lang.NullPointerException
>     at org.apache.hadoop.ozone.om.OzoneManager.getSCMSignedCert(OzoneManager.java:1372)
>     at org.apache.hadoop.ozone.om.OzoneManager.initializeSecurity(OzoneManager.java:1018)
>     at org.apache.hadoop.ozone.om.OzoneManager.omInit(OzoneManager.java:971)
>     at org.apache.hadoop.ozone.om.OzoneManager.createOm(OzoneManager.java:928)
>     at org.apache.hadoop.ozone.om.OzoneManager.main(OzoneManager.java:859)
> {code}
> I don't know what is the right validation rule here, but I am pretty sure that NPE should
be avoided and a meaningful error should be thrown. (and the behaviour should be the same
for scm and om)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message