[
https://issues.apache.org/jira/browse/HDFS-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899759#comment-13899759
]
Hadoop QA commented on HDFS-5891:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12628557/HDFS-5891.001.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/6126//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HDFS-Build/6126//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-hdfs.html
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/6126//console
This message is automatically generated.
> webhdfs should not try connecting the DN during redirection
> -----------------------------------------------------------
>
> Key: HDFS-5891
> URL: https://issues.apache.org/jira/browse/HDFS-5891
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Haohui Mai
> Assignee: Haohui Mai
> Attachments: HDFS-5891.000.patch, HDFS-5891.001.patch
>
>
> When the webhdfs server in NN serves an {{OPEN}} request, the NN will
> eventually redirect the request to a DN. The current implementation intends
> to choose the active DNs. The code always connects to the DN in a
> deterministic order to see whether it is active during redirection.
> Although it reduces the chance of the client from connecting to a failed DN,
> this is problematic because:
> # It has no guarantees that the client can connect to that DN even if the NN
> can connect to it.
> # It requires an additional network round-trip for every {{OPEN}} /
> {{CREATE}} request.
> This jira proposes that the NN should choose the DN based on the information
> of the data node manager.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
