hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HDFS-4479) logSync() with the FSNamesystem lock held in commitBlockSynchronization
Date Sun, 24 Feb 2013 21:58:12 GMT

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

Suresh Srinivas resolved HDFS-4479.

       Resolution: Fixed
    Fix Version/s: 1.2.0
     Hadoop Flags: Reviewed

I committed the patch to branch-1. Thank you Jing.
> logSync() with the FSNamesystem lock held in commitBlockSynchronization
> -----------------------------------------------------------------------
>                 Key: HDFS-4479
>                 URL: https://issues.apache.org/jira/browse/HDFS-4479
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>             Fix For: 1.2.0
>         Attachments: HDFS-4479.b1.001.patch, HDFS-4479.b1.002.patch
> In FSNamesystem#commitBlockSynchronization of branch-1, logSync() may be called when
the FSNamesystem lock is held. Similar with HDFS-4186, this may cause some performance issue.
> Since logSync is called right after the synchronization section, we can simply remove
the logSync call.

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

View raw message