[
https://issues.apache.org/jira/browse/HDFS-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811945#comment-13811945
]
Hudson commented on HDFS-5037:
------------------------------
SUCCESS: Integrated in Hadoop-Yarn-trunk #380 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/380/])
HDFS-5037. Active NN should trigger its own edit log rolls. Contributed by
Andrew Wang. (wang:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1538059)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSConfigKeys.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/ActiveState.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/resources/hdfs-default.xml
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestEditLogAutoroll.java
> 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
> Assignee: Andrew Wang
> Priority: Critical
> Fix For: 2.2.1
>
> Attachments: hdfs-5037-1.patch, hdfs-5037-2.patch, hdfs-5037-3.patch,
> hdfs-5037-4.patch, hdfs-5037-5.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)
