hadoop-mapreduce-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nitin Pawar <nitinpawar...@gmail.com>
Subject Re: Shutdown message while formatting hdfs
Date Mon, 24 Mar 2014 11:34:34 GMT
actual namenode format workflow is

1) start up namenode
2) wipe out old namespace info (namenode only)
3) create new namespace
4) create and save fsimage
5) create and save edit log
6) shut down the namenode

shutdown message you see is an intended one.
Once you format the namenode, you have to start it yourself.

Format and start are currently not supported in a single call as per my
understanding


On Mon, Mar 24, 2014 at 4:48 PM, Mahmood Naderan <nt_mahmood@yahoo.com>wrote:

> Hi,
> When I format the namenode, at the end I see a shutdown message. Is it
> important?
>
> $ hadoop namenode -format
> 14/03/24 15:42:38 INFO namenode.NameNode: STARTUP_MSG:
> /************************************************************
> STARTUP_MSG: Starting NameNode
> STARTUP_MSG:   host = tiger/192.168.1.5
> STARTUP_MSG:   args = [-format]
> STARTUP_MSG:   version = 1.2.1
> STARTUP_MSG:   build =
> https://svn.apache.org/repos/asf/hadoop/common/branches/branch-1.2 -r
> 1503152; compiled by 'mattf' on Mon Jul 22 15:23:09 PDT 2013
> STARTUP_MSG:   java = 1.7.0_51
> ************************************************************/
> 14/03/24 15:42:38 INFO util.GSet: Computing capacity for map BlocksMap
> 14/03/24 15:42:38 INFO util.GSet: VM type       = 64-bit
> 14/03/24 15:42:38 INFO util.GSet: 2.0% max memory = 1005060096
> 14/03/24 15:42:38 INFO util.GSet: capacity      = 2^21 = 2097152 entries
> 14/03/24 15:42:38 INFO util.GSet: recommended=2097152, actual=2097152
> 14/03/24 15:42:38 INFO namenode.FSNamesystem: fsOwner=hadoop
> 14/03/24 15:42:39 INFO namenode.FSNamesystem: supergroup=supergroup
> 14/03/24 15:42:39 INFO namenode.FSNamesystem: isPermissionEnabled=true
> 14/03/24 15:42:39 INFO namenode.FSNamesystem:
> dfs.block.invalidate.limit=100
> 14/03/24 15:42:39 INFO namenode.FSNamesystem: isAccessTokenEnabled=false
> accessKeyUpdateInterval=0 min(s), accessTokenLifetime=0 min(s)
> 14/03/24 15:42:39 INFO namenode.FSEditLog:
> dfs.namenode.edits.toleration.length = 0
> 14/03/24 15:42:39 INFO namenode.NameNode: Caching file names occuring more
> than 10 times
> 14/03/24 15:42:39 INFO common.Storage: Image file
> /data/hadoop.hdfs/dir/current/fsimage of size 112 bytes saved in 0 seconds.
> 14/03/24 15:42:39 INFO namenode.FSEditLog: closing edit log: position=4,
> editlog=/data/hadoop.hdfs/dir/current/edits
> 14/03/24 15:42:39 INFO namenode.FSEditLog: close success: truncate to 4,
> editlog=/data/hadoop.hdfs/dir/current/edits
> 14/03/24 15:42:39 INFO common.Storage: Storage directory
> /data/hadoop.hdfs/dir has been successfully formatted.
> 14/03/24 15:42:39 INFO namenode.NameNode: SHUTDOWN_MSG:
> /************************************************************
> SHUTDOWN_MSG: Shutting down NameNode at tiger/192.168.1.5
> ************************************************************/
>
> Regards,
> Mahmood
>



-- 
Nitin Pawar

Mime
View raw message