[
https://issues.apache.org/jira/browse/HDFS-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181014#comment-13181014
]
Hari Mankude commented on HDFS-2753:
------------------------------------
Hi Aaron,
This is the info from NN
Started: Fri Jan 06 00:32:04 UTC 2012
Version: 0.24.0-SNAPSHOT, 1227260 ---> version number.
Doing another clean build to make sure that the problem exists.
Seems like commenting out the optimization in processReport() fixes the
problem.
// To minimize startup time, we discard any second (or later) block
reports
// that we receive while still in startup phase.
if (namesystem.isInStartupSafeMode() && node.numBlocks() > 0) {
NameNode.stateChangeLog.info("BLOCK* processReport: "
+ "discarded non-initial block report from " + nodeID.getName()
+ " because namenode still in startup phase");
return;
}
> Standby namenode stuck in safemode during a failover
> ----------------------------------------------------
>
> Key: HDFS-2753
> URL: https://issues.apache.org/jira/browse/HDFS-2753
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha, name-node
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Hari Mankude
> Assignee: Hari Mankude
>
> Write traffic initiated from the client. Manual failover is done by killing
> NN and converting a different standby to active. NN is restarted as standby.
> The restarted standby stays in safemode forever. More information in the
> description.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
