[
https://issues.apache.org/jira/browse/HDFS-5855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886697#comment-13886697
]
Tsz Wo (Nicholas), SZE commented on HDFS-5855:
----------------------------------------------
Hi Vinay, only Standby NN could be restarted in rolling upgrade (otherwise,
there is downtime). For restarting Standby NN, HDFS-5835 has already addressed
the problem you mentioned here. Could you take a look?
> Reading edits should not stop at UpgradeMarker for normal restart of the
> namenode
> ---------------------------------------------------------------------------------
>
> Key: HDFS-5855
> URL: https://issues.apache.org/jira/browse/HDFS-5855
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: datanode, ha, hdfs-client, namenode
> Reporter: Vinay
>
> As mentioned
> [here|https://issues.apache.org/jira/browse/HDFS-5645?focusedCommentId=13867530&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13867530]
> in HDFS-5645 NameNode restart will stop reading Edits at UpgradeMarker. But
> this should happen only if namenode is rolling back from upgrade.
> There is also a possibility that namenode could get restarted after rolling
> upgrade started. This should not rollback everything.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
