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

Hudson commented on HDFS-8273:
------------------------------

FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #178 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/178/])
HDFS-8273. FSNamesystem#Delete() should not call logSync() when holding the 
lock. Contributed by Haohui Mai. (wheat9: rev 
c79e7f7d997596e0c38ae4cddff2bd0910581c16)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSDirDeleteOp.java


> FSNamesystem#Delete() should not call logSync() when holding the lock
> ---------------------------------------------------------------------
>
>                 Key: HDFS-8273
>                 URL: https://issues.apache.org/jira/browse/HDFS-8273
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.7.0
>            Reporter: Jing Zhao
>            Assignee: Haohui Mai
>            Priority: Blocker
>             Fix For: 2.7.1
>
>         Attachments: HDFS-8273.000.patch, HDFS-8273.001.patch
>
>
> HDFS-7573 moves the logSync call inside of the write lock by accident. We 
> should move it out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to