[
https://issues.apache.org/jira/browse/HDFS-8178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16914112#comment-16914112
]
Istvan Fajth commented on HDFS-8178:
------------------------------------
Added a new patch that addresses the synchronized access issue (findbugs), and
the whitespace issue, I have checked the test, it seem to be failing due to a
timeout, I haven't find the source of it yet, and locally I need significant
increases in the timeouts in order this test to pass, so let's wait for a
second run and see if the problem is still there. If it is then it will need
further investigation to be sure what is causing the delay. For the first sight
for me it is not obvious how the changes can cause a significant delay, but the
timeout happens in the test when it waits for a NameNode to become Active, so
it might be related.
> QJM doesn't move aside stale inprogress edits files
> ---------------------------------------------------
>
> Key: HDFS-8178
> URL: https://issues.apache.org/jira/browse/HDFS-8178
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: qjm
> Reporter: Zhe Zhang
> Assignee: Istvan Fajth
> Priority: Major
> Labels: BB2015-05-TBR
> Attachments: HDFS-8178.000.patch, HDFS-8178.002.patch,
> HDFS-8178.003.patch, HDFS-8178.004.patch, HDFS-8178.005.patch,
> HDFS-8178.006.patch
>
>
> When a QJM crashes, the in-progress edit log file at that time remains in the
> file system. When the node comes back, it will accept new edit logs and those
> stale in-progress files are never cleaned up. QJM treats them as regular
> in-progress edit log files and tries to finalize them, which potentially
> causes high memory usage. This JIRA aims to move aside those stale edit log
> files to avoid this scenario.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
