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

Hadoop QA commented on HDFS-5029:
---------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12597172/HDFS-5029.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:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any 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/4796//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4796//console

This message is automatically generated.
                
> Token operations should not block read operations
> -------------------------------------------------
>
>                 Key: HDFS-5029
>                 URL: https://issues.apache.org/jira/browse/HDFS-5029
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>         Attachments: HDFS-5029.branch-23.patch, HDFS-5029.patch, 
> HDFS-5029.patch
>
>
> Token operations unnecessarily obtain the write lock on the namespace.  Edits 
> for token operations are independent of edits for other namespace write 
> operations, and the edits have no ordering requirement with respect to 
> namespace changes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to