Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 28 Feb 2012 07:41:57 +0000 (UTC)
From: "Aaron T. Myers (Assigned) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1199589806.27073.1330414917549.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1546748538.26444.1330400514587.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (HDFS-3020) Auto-logSync based on edit log buffer
 size broken
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aaron T. Myers reassigned HDFS-3020:
------------------------------------

    Assignee: Todd Lipcon
    
> 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
>         Attachments: 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