[
https://issues.apache.org/jira/browse/HDFS-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970223#action_12970223
]
Sanjay Radia commented on HDFS-1508:
------------------------------------
I don't see a problem with the entering the safemode except that it wierd thing
(a cmd that has has a side effect - but I agree that a failure of saveNamespace
imples that
the storage has serious problem).
Q. If saveNamespace fails, why will checkpoint run into a problem? There will
be a tmp dir that has probably stuck around.
Q. In the past a saveNamespace in progress aborted a checkpoint because the NN
was in safemode. With this jira is there a valriable called
saveNamespaceInProgress that
will be used to abort the 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, savenamespaceWithoutSafemode3.txt,
> savenamespaceWithoutSafemode4.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.
