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

Hudson commented on HDFS-3020:
------------------------------

Integrated in Hadoop-Mapreduce-0.23-Commit #620 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Commit/620/])
    HDFS-3020. Fix editlog to automatically sync when buffer is full. 
Contributed by Todd Lipcon. (Revision 1295241)

     Result = ABORTED
todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1295241
Files : 
* 
/hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/EditsDoubleBuffer.java
* 
/hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSEditLog.java
* 
/hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestEditLog.java

                
> Auto-logSync based on edit log buffer size broken
> -------------------------------------------------
>
>                 Key: HDFS-3020
>                 URL: https://issues.apache.org/jira/browse/HDFS-3020
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.22.0, 0.23.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Critical
>             Fix For: 0.24.0, 0.23.3
>
>         Attachments: hdfs-3020.txt, hdfs-3020.txt, hdfs-3020.txt
>
>
> HDFS-1112 added a feature whereby the edit log automatically calls logSync() 
> if the buffered data crosses a threshold. However, the code checks 
> {{bufReady.size()}} rather than {{bufCurrent.size()}} -- which is incorrect 
> since the writes themselves go into {{bufCurrent}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to