[
https://issues.apache.org/jira/browse/HDFS-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13218381#comment-13218381
]
Todd Lipcon commented on HDFS-3020:
-----------------------------------
bq. Does this mean that the editlog is being synced only during rolling of
editlogs?
Nope, it's being synced OK for any operations that call {{logSync}}. It's just
that the functionality of HDFS-1112 isn't working -- so, for example, if you
start a NN and then only perform getBlockLocations calls, it may fill up the
log buffer until the NN is entirely out of RAM.
I'll update the patch against trunk - the previous patch was against HA branch
but I forgot that the APIs have been changed a little bit, so the test didn't
compile.
> 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
