You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Jing Zhao (JIRA)" <ji...@apache.org> on 2014/02/25 23:01:20 UTC

[jira] [Resolved] (HDFS-6000) Avoid saving namespace when starting rolling upgrade

     [ https://issues.apache.org/jira/browse/HDFS-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jing Zhao resolved HDFS-6000.
-----------------------------

      Resolution: Fixed
    Hadoop Flags: Reviewed

I've committed this. Thanks for the review, Nicholas and Vinay!

> Avoid saving namespace when starting rolling upgrade
> ----------------------------------------------------
>
>                 Key: HDFS-6000
>                 URL: https://issues.apache.org/jira/browse/HDFS-6000
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode, ha, hdfs-client, namenode
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>         Attachments: HDFS-6000.000.patch, HDFS-6000.001.patch, HDFS-6000.002.patch, HDFS-6000.003.patch
>
>
> Currently when administrator sends the "rollingUpgrade start" command to the active NN, the NN will trigger a checkpoint (the rollback fsimage). This will cause NN not able to serve for a period of time.
> An alternative way is just to let the SBN do checkpoint, and rename the first checkpoint after starting the rolling upgrade to rollback image. After the rollback image is on both the ANN and the SBN, administrator can start upgrading the software.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)