hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinayakumar B (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6000) Avoid saving namespace when starting rolling upgrade
Date Tue, 25 Feb 2014 06:19:24 GMT

    [ https://issues.apache.org/jira/browse/HDFS-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911293#comment-13911293
] 

Vinayakumar B commented on HDFS-6000:
-------------------------------------

Changes looks good.

Small nit:
{code}
+  public synchronized void saveNamespace(FSNamesystem source, NameNodeFile nnf,
+      Canceler canceler) throws IOException, SaveNamespaceCancelledException {
{code}
I think explicitly mentioning {{SaveNamespaceCancelledException}} in throws clause may not
be required. Do you agree?

> 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
>
>
> 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)

Mime
View raw message