[
https://issues.apache.org/jira/browse/HDFS-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509473#comment-13509473
]
Hadoop QA commented on HDFS-4238:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12555873/hdfs-4238.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{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/3596//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3596//console
This message is automatically generated.
> [HA] Standby namenode should not do purging of shared storage edits.
> --------------------------------------------------------------------
>
> Key: HDFS-4238
> URL: https://issues.apache.org/jira/browse/HDFS-4238
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha
> Affects Versions: 3.0.0, 2.0.2-alpha
> Reporter: Vinay
> Assignee: Todd Lipcon
> Attachments: hdfs-4238.txt, hdfs-4238.txt
>
>
> This happened in our cluster,
> >> Standby NN was keep doing checkpoint every one hour and uploading to
> >> Active NN was continuously failing due to some kerberos issue and nobody
> >> noticed this, since Active was servicing properly.
> >> Active NN was up for long time with fsimage having very least transaction.
> >> Standby NN has saved the checkpoint in its name dir and purged the txns >
> >> 1000000 from shared storage ( includes edits which are not present in
> >> Active NN's fsimage)
> >> After some time Active NN is restarted and StandBy NN switched to Active.
> Now current Standby not able to load any edits from shared storage, as
> expected edits are not present in shared storage. Its keep running idle.
> So {{editLog.purgeLogsOlderThan(purgeLogsFrom);}} always should be called
> from Active NameNode.
--
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
