hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-3280) DFSOutputStream.sync should not be synchronized
Date Sat, 14 Apr 2012 02:53:17 GMT

     [ https://issues.apache.org/jira/browse/HDFS-3280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Todd Lipcon updated HDFS-3280:

       Resolution: Fixed
    Fix Version/s: 2.0.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Committed to branch-2 (as noted above, this problem isn't present in trunk since sync() was

Thanks also to Matteo Bertozzi and Jon Hsieh for their help tracking this issue down.
> DFSOutputStream.sync should not be synchronized
> -----------------------------------------------
>                 Key: HDFS-3280
>                 URL: https://issues.apache.org/jira/browse/HDFS-3280
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 2.0.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Critical
>             Fix For: 2.0.0
>         Attachments: hdfs-3280.txt
> HDFS-895 added an optimization to make hflush() much faster by unsynchronizing it. But,
we forgot to un-synchronize the deprecated {{sync()}} wrapper method. This makes the HBase
WAL really slow on 0.23+ since it doesn't take advantage of HDFS-895 anymore.

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


View raw message