[
https://issues.apache.org/jira/browse/HDFS-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486702#comment-13486702
]
Aaron T. Myers commented on HDFS-3980:
--------------------------------------
bq. i) Even If we configure IP, It should be resolved rite.(as I mentioned in
defect, host-name resolution should be done rite.).
I suppose we could perform reverse DNS on the configured fs.defaultFS, but I
must admit that I don't understand the use case for configuring an explicit IP
address when the node in question does indeed have an externally resolvable
hostname that could be used.
bq. NPE,can we address NPE ?
I'm pretty sure that the NPE itself is actually a bug in the JDK. We might be
able to check for a specific Hadoop misconfiguration at a higher level so that
we never reach the code that will cause the NPE, but doing so in such a way
that would cover all possible cases of this NPE might prove difficult.
> NPE in HttpURLConnection.java while starting SecondaryNameNode.
> ---------------------------------------------------------------
>
> Key: HDFS-3980
> URL: https://issues.apache.org/jira/browse/HDFS-3980
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: security
> Affects Versions: 3.0.0, 2.0.1-alpha
> Reporter: Brahma Reddy Battula
> Priority: Critical
> Attachments: core-site.xml, hdfs-site.xml
>
>
> Scenario:
> ========
> I started secure cluster by going thru following..
> https://ccp.cloudera.com/display/CDHDOC/CDH3+Security+Guide..
> Here SecondaryNamenode is getting shutdown by throwing NPE..
> Please correct me If I am wrong...
> Will attach conf and logs..
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
