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-5329) Update FSNamesystem#getListing() to handle inode path in startAfter token
Date Fri, 11 Oct 2013 02:13:42 GMT

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

Hadoop QA commented on HDFS-5329:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12607919/HDFS-5329.2.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 1 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}.  The javadoc tool did not generate any warning messages.

    {color:red}-1 eclipse:eclipse{color}.  The patch failed to build with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
1.3.9) warnings.

        {color:red}-1 release audit{color}.  The applied patch generated 1 release audit warnings.

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

                  org.apache.hadoop.hdfs.server.datanode.fsdataset.TestAvailableSpaceVolumeChoosingPolicy

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/5167//testReport/
Release audit warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/5167//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5167//console

This message is automatically generated.

> Update FSNamesystem#getListing() to handle inode path in startAfter token
> -------------------------------------------------------------------------
>
>                 Key: HDFS-5329
>                 URL: https://issues.apache.org/jira/browse/HDFS-5329
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>            Reporter: Brandon Li
>            Assignee: Brandon Li
>         Attachments: HDFS-5329.1.patch, HDFS-5329.2.patch, HDFS-5329.3.patch, HDFS-5329.patch
>
>
> This is to support network protocols which can't use file name as the token to resume
directory listing. 
> NFS gateway doesn't know the name of startAfter and has to use inode id instead. NFS
protocol uses readdir and readdirplus to list directory content. In the response, each dirent
has an 8-byte number verifier.
> To list the content of large directories, NFS client sends multiple readdir or readdirplus
requests to NFS gateway with one verifier(resume point) in the request. The verifier is basically
of the same usage as "startAfter" in getListing. Since NFSv3 uses file handle to communicate
and doesn't know the file name. NFS gateway has to use the inode id path as "startAfter" when
sending getList request to NN, however NN currently expects "startAfter" to be just a file
name. As a result, NFS gateway can't list the content of large directories.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message