[
https://issues.apache.org/jira/browse/HDFS-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809901#comment-13809901
]
Hadoop QA commented on HDFS-5037:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12611233/hdfs-5037-1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/5318//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5318//console
This message is automatically generated.
> 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
> Attachments: hdfs-5037-1.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)
