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

Wei-Chiu Chuang updated HDFS-8178:
----------------------------------
    Fix Version/s: 3.1.3
       Resolution: Fixed
           Status: Resolved  (was: Patch Available)

Pushed to branch-3.1 as well. Thanks [~pifta] and [~zhz]!

> 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
>             Fix For: 3.3.0, 3.2.1, 3.1.3
>
>         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, HDFS-8178.007.patch, HDFS-8178.008.addendum, 
> HDFS-8178.008.merged, HDFS-8178.008.patch, HDFS-8178.branch-3.1.patch, 
> HDFS-8178.branch-3.2.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

Reply via email to