hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benoy Antony (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7303) If there are multiple datanodes on the same host, then only one datanode is listed on the NN UI’s datanode tab
Date Fri, 31 Oct 2014 17:35:34 GMT

    [ https://issues.apache.org/jira/browse/HDFS-7303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192136#comment-14192136
] 

Benoy Antony commented on HDFS-7303:
------------------------------------

Thanks [~wheat9] for the comments. I agree with you and understand that its a bug. 
But since the value was part of the JSON output, we should be mindful of compatibility issues.

 As an example, if any external tool was using the hostname based on the JSON output to construct
a URL as http://<datanode-host-name-from-JSON>:someport/blah, then that will fail if
we add port to JSON output. It will become http://<datanode-host-name-from-JSON:datanodeport>:someport/blah

That's why I am trying to keep the same behavior if there is only one data node on a host
(which is the normal case). 

>  If there are multiple datanodes on the same host, then only one datanode is listed on
the NN UI’s datanode tab
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-7303
>                 URL: https://issues.apache.org/jira/browse/HDFS-7303
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.5.1
>            Reporter: Benoy Antony
>            Assignee: Benoy Antony
>            Priority: Minor
>         Attachments: HDFS-7303.patch, HDFS-7303.patch
>
>
> If you start multiple datanodes on different ports on the the same host, only one of
them appears in the NN UI’s datanode tab.
> While this is not a common scenario, there are still scenarios where you need to start
multiple datanodes on the same host.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message