Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 29 Feb 2012 07:03:57 +0000 (UTC)
From: "Todd Lipcon (Updated) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1417352871.1648.1330499038007.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <296475267.29872.1330457866290.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HDFS-3025) Automatic log sync shouldn't happen
 inside logEdit path
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Todd Lipcon updated HDFS-3025:
------------------------------

    Status: Open  (was: Patch Available)

Looks like the test failure is legit. I'll look into this and post an updated patch.
                
> Automatic log sync shouldn't happen inside logEdit path
> -------------------------------------------------------
>
>                 Key: HDFS-3025
>                 URL: https://issues.apache.org/jira/browse/HDFS-3025
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node, performance
>    Affects Versions: 0.23.3
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: hdfs-3025.txt
>
>
> HDFS-3020 fixes the "automatic log sync" functionality so that, when logEdits is called without log sync, it eventually triggers a sync. That sync ends up being inline, though, which means the FSN lock is usually held during it. This causes a bunch of threads to pile up.
> Instead, we should have it just set a "syncNeeded" flag and trigger a sync from another thread which isn't holding the lock (or from the same thread using a "logSyncIfNeeded" call).
> (credit to the FB branch for this idea)

--
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