[
https://issues.apache.org/jira/browse/HDFS-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244758#comment-13244758
]
Hadoop QA commented on HDFS-3148:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12521013/hdfs-3148.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any 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:
org.apache.hadoop.hdfs.server.namenode.ha.TestPipelinesFailover
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/2161//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2161//console
This message is automatically generated.
> The client should be able to use multiple local interfaces for data transfer
> ----------------------------------------------------------------------------
>
> Key: HDFS-3148
> URL: https://issues.apache.org/jira/browse/HDFS-3148
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs client
> Reporter: Eli Collins
> Assignee: Eli Collins
> Attachments: hdfs-3148-b1.txt, hdfs-3148-b1.txt, hdfs-3148.txt,
> hdfs-3148.txt, hdfs-3148.txt
>
>
> HDFS-3147 covers using multiple interfaces on the server (Datanode) side.
> Clients should also be able to utilize multiple *local* interfaces for
> outbound connections instead of always using the interface for the local
> hostname. This can be accomplished with a new configuration parameter
> ({{dfs.client.local.interfaces}}) that accepts a list of interfaces the
> client should use. Acceptable configuration values are the same as the
> {{dfs.datanode.available.interfaces}} parameter. The client binds its socket
> to a specific interface, which enables outbound traffic to use that
> interface. Binding the client socket to a specific address is not sufficient
> to ensure egress traffic uses that interface. Eg if multiple interfaces are
> on the same subnet the host requires IP rules that use the source address
> (which bind sets) to select the destination interface. The SO_BINDTODEVICE
> socket option could be used to select a specific interface for the connection
> instead, however it requires JNI (is not in Java's SocketOptions) and root
> access, which we don't want to require clients have.
> Like HDFS-3147, the client can use multiple local interfaces for data
> transfer. Since the client already cache their connections to DNs choosing a
> local interface at random seems like a good policy. Users can also pin a
> specific client to a specific interface by specifying just that interface in
> dfs.client.local.interfaces.
> This change was discussed in HADOOP-6210 a while back, and is actually
> useful/independent of the other HDFS-3140 changes.
--
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
