hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3020) Auto-logSync based on edit log buffer size broken
Date Thu, 01 Mar 2012 20:59:58 GMT

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

Tsz Wo (Nicholas), SZE commented on HDFS-3020:

> The latest patch was against a non-trunk branch so it didn't apply quite cleanly.

Then, which one is the committed patch for trunk?
> 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


View raw message