hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1980) 'dfsadmin -safemode enter' should prevent the namenode from leaving safemode automatically after startup
Date Tue, 16 Dec 2008 02:29:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656851#action_12656851

Konstantin Shvachko commented on HADOOP-1980:

The requirement here as I understand it is to make it possible to extend the safe mode indefinitely.
First thing to do is just to start the name-node with a large extension or a >1 threshold.
I guess this does not work if the name-node has already been started but the administrator
needs to keep it in safe mode longer than the extension.
Then why don't we just set really long extension in this case.
Or even better provide an explicit option to extend safe mode from the admin command.
hadoop dfsadmin -safemode extend
This will be much simpler patch, which would satisfy all the requirements and will have clear
user api.
Otherwise it seems rather strange from a user point of view: in order to get infinite safe
mode one should enter safe mode again although it is already on.

> 'dfsadmin -safemode enter' should prevent the namenode from leaving safemode automatically
after startup
> --------------------------------------------------------------------------------------------------------
>                 Key: HADOOP-1980
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1980
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>            Reporter: Koji Noguchi
>            Assignee: Raghu Angadi
>            Priority: Minor
>         Attachments: HADOOP-1980.patch
> When debugging, I'd like to be able to intentionally keep the FS in a safemode. (For
example, when looking at HADOOP-1978).
> Also, it'll be nice if the namenode can still update the webUI/report when it hits the

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message