hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-1690) Name Node should not process format command while it is running.
Date Tue, 29 Mar 2011 06:49:05 GMT

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

Konstantin Shvachko commented on HDFS-1690:
-------------------------------------------

NameNode should not format partially. If the lock file is present the format command should
warn and exit. I believe this is what it does. Does it not?
The lock file is the right way to determine that the NameNode is running, not the web server.

> Name Node should not process format command while it is running.
> ----------------------------------------------------------------
>
>                 Key: HDFS-1690
>                 URL: https://issues.apache.org/jira/browse/HDFS-1690
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.20.1, 0.20.2, 0.21.0
>            Reporter: Uma Maheswara Rao G
>            Assignee: Uma Maheswara Rao G
>         Attachments: HDFS-1690.patch
>
>
> Currently NameNode allows format command while it running. In this case the command is
executed partially (Lock file is deleted) and an exception thrown. Because of this Name Node
should be formatted after restart. This sort of cases can happen accidentally. To prevent
such cases Name Node should not execute the format command partially while it is running.
It can stright away throw exception/log saying, Name Node is running.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message