hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3150) Add option for clients to contact DNs via hostname
Date Tue, 14 Aug 2012 03:27:38 GMT

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

Hadoop QA commented on HDFS-3150:
---------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12540786/hdfs-3150.txt
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 10 new or modified test files.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 eclipse:eclipse.  The patch built with eclipse:eclipse.

    -1 findbugs.  The patch appears to introduce 2 new Findbugs (version 1.3.9) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit
warnings.

    -1 core tests.  The patch failed these unit tests in hadoop-hdfs-project/hadoop-hdfs:

                  org.apache.hadoop.hdfs.server.namenode.metrics.TestNameNodeMetrics
                  org.apache.hadoop.hdfs.web.TestWebHDFS
                  org.apache.hadoop.hdfs.TestPersistBlocks

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/2996//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/2996//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-hdfs.html
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2996//console

This message is automatically generated.
                
> Add option for clients to contact DNs via hostname
> --------------------------------------------------
>
>                 Key: HDFS-3150
>                 URL: https://issues.apache.org/jira/browse/HDFS-3150
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: data-node, hdfs client
>    Affects Versions: 1.0.0, 2.0.0-alpha
>            Reporter: Eli Collins
>            Assignee: Eli Collins
>             Fix For: 1.1.0
>
>         Attachments: hdfs-3150-b1.txt, hdfs-3150-b1.txt, hdfs-3150.txt, hdfs-3150.txt,
hdfs-3150.txt
>
>
> The DN listens on multiple IP addresses (the default {{dfs.datanode.address}} is the
wildcard) however per HADOOP-6867 only the source address (IP) of the registration is given
to clients. HADOOP-985 made clients access datanodes by IP primarily to avoid the latency
of a DNS lookup, this had the side effect of breaking DN multihoming (the client can not route
the IP exposed by the NN if the DN registers with an interface that has a cluster-private
IP). To fix this let's add back the option for Datanodes to be accessed by hostname.
> This can be done by:
> # Modifying the primary field of the Datanode descriptor to be the hostname, or 
> # Modifying Client/Datanode <-> Datanode access use the hostname field instead
of the IP
> Approach #2 does not require an incompatible client protocol change, and is much less
invasive. It minimizes the scope of modification to just places where clients and Datanodes
connect, vs changing all uses of Datanode identifiers.
> New client and Datanode configuration options are introduced:
> - {{dfs.client.use.datanode.hostname}} indicates all client to datanode connections should
use the datanode hostname (as clients outside cluster may not be able to route the IP)
> - {{dfs.datanode.use.datanode.hostname}} indicates whether Datanodes should use hostnames
when connecting to other Datanodes for data transfer
> If the configuration options are not used, there is no change in the current behavior.

--
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

        

Mime
View raw message