You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2013/07/26 17:27:49 UTC

[jira] [Created] (HDFS-5037) Active NN should trigger its own edit log rolls

Todd Lipcon created HDFS-5037:
---------------------------------

             Summary: Active NN should trigger its own edit log rolls
                 Key: HDFS-5037
                 URL: https://issues.apache.org/jira/browse/HDFS-5037
             Project: Hadoop HDFS
          Issue Type: Improvement
          Components: ha, namenode
    Affects Versions: 3.0.0, 2.1.0-beta
            Reporter: Todd Lipcon


We've seen cases where the SBN/2NN went down, and then users accumulated very very large edit log segments. This causes a slow startup time because the last edit log segment must be read fully to recover it before the NN can start up again. Additionally, in the case of QJM, it can trigger timeouts on recovery or edit log syncing because the very-large segment has to get processed within a certain time bound.

We could easily improve this by having the NN trigger its own edit log rolls on a configurable size (eg every 256MB)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira