[
https://issues.apache.org/jira/browse/HDFS-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HDFS-2753:
------------------------------
Attachment: hdfs-2753.txt
Attached patch includes a new unit test which triggered the bug as described.
I also fixed several issues in the patch that Hari had uploaded:
- should use javadoc style comments for member variables
- no need to introduce a new function {{processedBlockReport}} in
{{DatanodeDescriptor}} since we already have {{receivedBlockReport}} for the
same purpose
- the new function was never being called, since it was mistakenly put inside
the "skip processing" code path instead of the "do processing" code path
- renamed {{firstBlockReport()}} function to {{isFirstBlockReport()}} since it
returns a boolean
> 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, hdfs-2753.txt
>
>
> 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
