You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "dhruba borthakur (JIRA)" <ji...@apache.org> on 2010/12/02 08:05:11 UTC
[jira] Updated: (HDFS-1508) Ability to do savenamespace without
being in safemode
[ https://issues.apache.org/jira/browse/HDFS-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HDFS-1508:
-----------------------------------
Attachment: savenamespaceWithoutSafemode2.txt
This patch introduces a "force" option to the saveNamespace command. If this option is set, then the saveNamespace command is executed even if the namenode is not in safemode. The ClientProtocol number is bumped up by one.
I am manually testing this patch with concurrent checkpointing and saveNamespace. I am unable to write a unit test that would trigger all or any of the races between saveNamespace and checkpoint.
> Ability to do savenamespace without being in safemode
> -----------------------------------------------------
>
> Key: HDFS-1508
> URL: https://issues.apache.org/jira/browse/HDFS-1508
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: name-node
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Attachments: savenamespaceWithoutSafemode.txt, savenamespaceWithoutSafemode2.txt
>
>
> In the current code, the administrator can run savenamespace only after putting the namenode in safemode. This means that applications that are writing to HDFS encounters errors because the NN is in safemode. We would like to allow saveNamespace even when the namenode is not in safemode.
> The savenamespace command already acquires the FSNamesystem writelock. There is no need to require that the namenode is in safemode too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.