[
https://issues.apache.org/jira/browse/HDFS-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000714#comment-13000714
]
Suresh Srinivas commented on HDFS-1669:
---------------------------------------
With patch TestHftpFileSystem and TestFiHftp passes. Here is the testpatch
result:
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 6 new or
modified tests.
[exec]
[exec] -1 javadoc. The javadoc tool appears to have generated 1
warning messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 release audit. The applied patch does not increase the
total number of release audit warnings.
[exec]
[exec] +1 system tests framework. The patch passed system tests
framework compile.
The javadoc warning is unrelated to the patch.
> Federation: Datanode servlets need information about the namenode to service
> the request
> ----------------------------------------------------------------------------------------
>
> Key: HDFS-1669
> URL: https://issues.apache.org/jira/browse/HDFS-1669
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: data-node, name-node
> Affects Versions: Federation Branch
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
> Fix For: Federation Branch
>
> Attachments: HDFS-1669.patch
>
>
> Prior to federation datanode had only one namenode. In servlets hosted on
> datanode, a DFSClient was created to the only namenode to serve the request.
> However with federation datanode has multiple namenodes. When a request is
> redirected to a datanode, it does not know which namenode to use for
> servicing the request.
> This results in TestHftpFileSystem failure.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
