[jira] [Commented] (HDFS-2859) LOCAL_ADDRESS_MATCHER.match has NPE when called from DFSUtil.getSuffixIDs when the host is incorrect
[ https://issues.apache.org/jira/browse/HDFS-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198765#comment-13198765 ] Hudson commented on HDFS-2859: -- Integrated in Hadoop-Hdfs-HAbranch-build #66 (See [https://builds.apache.org/job/Hadoop-Hdfs-HAbranch-build/66/]) HDFS-2859. LOCAL_ADDRESS_MATCHER.match has NPE when called from DFSUtil.getSuffixIDs when the host is incorrect. Contributed by Bikas Saha. todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1239356 Files : * /hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/CHANGES.HDFS-1623.txt * /hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSUtil.java > LOCAL_ADDRESS_MATCHER.match has NPE when called from DFSUtil.getSuffixIDs > when the host is incorrect > > > Key: HDFS-2859 > URL: https://issues.apache.org/jira/browse/HDFS-2859 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Bikas Saha >Assignee: Bikas Saha >Priority: Minor > Fix For: HA branch (HDFS-1623) > > Attachments: HDFS-2859.HDFS-1623.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2859) LOCAL_ADDRESS_MATCHER.match has NPE when called from DFSUtil.getSuffixIDs when the host is incorrect
[ https://issues.apache.org/jira/browse/HDFS-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198373#comment-13198373 ] Bikas Saha commented on HDFS-2859: -- Thanks! > LOCAL_ADDRESS_MATCHER.match has NPE when called from DFSUtil.getSuffixIDs > when the host is incorrect > > > Key: HDFS-2859 > URL: https://issues.apache.org/jira/browse/HDFS-2859 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Bikas Saha >Assignee: Bikas Saha >Priority: Minor > Fix For: HA branch (HDFS-1623) > > Attachments: HDFS-2859.HDFS-1623.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2859) LOCAL_ADDRESS_MATCHER.match has NPE when called from DFSUtil.getSuffixIDs when the host is incorrect
[ https://issues.apache.org/jira/browse/HDFS-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198193#comment-13198193 ] Todd Lipcon commented on HDFS-2859: --- bq. A general question I have is whether it is ok for certain name node hosts to be unresolved during startup. I guess it might be ok because some machines might legitimately be out of service and disconnected from the network. I don't think it's OK -- though a loud warning might be enough. Even if the host is down/disconnected, we'd expect the domain name to be around. The patch here looks good, though. +1 > LOCAL_ADDRESS_MATCHER.match has NPE when called from DFSUtil.getSuffixIDs > when the host is incorrect > > > Key: HDFS-2859 > URL: https://issues.apache.org/jira/browse/HDFS-2859 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Bikas Saha >Assignee: Bikas Saha >Priority: Minor > Attachments: HDFS-2859.HDFS-1623.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2859) LOCAL_ADDRESS_MATCHER.match has NPE when called from DFSUtil.getSuffixIDs when the host is incorrect
[ https://issues.apache.org/jira/browse/HDFS-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197339#comment-13197339 ] Bikas Saha commented on HDFS-2859: -- Based on the response to my question above I may resolve [HDFS-2858|https://issues.apache.org/jira/browse/HDFS-2858] with this patch. If its ok to have erroneous hosts then it might work to simply log the exception and proceed. > LOCAL_ADDRESS_MATCHER.match has NPE when called from DFSUtil.getSuffixIDs > when the host is incorrect > > > Key: HDFS-2859 > URL: https://issues.apache.org/jira/browse/HDFS-2859 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ha, name-node >Affects Versions: HA branch (HDFS-1623) >Reporter: Bikas Saha >Assignee: Bikas Saha >Priority: Minor > Attachments: HDFS-2859.HDFS-1623.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-2859) LOCAL_ADDRESS_MATCHER.match has NPE when called from DFSUtil.getSuffixIDs when the host is incorrect
[ https://issues.apache.org/jira/browse/HDFS-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196333#comment-13196333 ] Bikas Saha commented on HDFS-2859: -- I was testing startup of an HA name node with an incorrect host and it crashed with an NPE here. > LOCAL_ADDRESS_MATCHER.match has NPE when called from DFSUtil.getSuffixIDs > when the host is incorrect > > > Key: HDFS-2859 > URL: https://issues.apache.org/jira/browse/HDFS-2859 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Bikas Saha >Assignee: Bikas Saha > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira