[
https://issues.apache.org/jira/browse/HDFS-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182746#comment-13182746
]
Todd Lipcon commented on HDFS-2753:
-----------------------------------
It seems like this should be easy to produce -- just so long as there is some
write traffic while one of the nodes is down, then the blockReceived calls will
get queued up in the BPServiceActor, and when it re-registers they will all be
flushed before the first block report, triggering the bug. I will try to write
a test.
> 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: Sub-task
> Components: ha, name-node
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Hari Mankude
> Assignee: Hari Mankude
> Attachments: HDFS-2753.patch
>
>
> 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
