Hello Onder,

The "successfully formatted" line tells me that the HDFS format worked 
successfully, so I think all is well.  Perhaps that wiki page has some outdated 
information.

--Chris Nauroth

From: Onder SEZGIN <ondersez...@gmail.com<mailto:ondersez...@gmail.com>>
Reply-To: "user@hadoop.apache.org<mailto:user@hadoop.apache.org>" 
<user@hadoop.apache.org<mailto:user@hadoop.apache.org>>
Date: Monday, September 28, 2015 at 1:18 AM
To: "user@hadoop.apache.org<mailto:user@hadoop.apache.org>" 
<user@hadoop.apache.org<mailto:user@hadoop.apache.org>>
Subject: question regarding Hadoop2OnWindows guide

Hi,

I follow the guide on this link,

https://wiki.apache.org/hadoop/Hadoop2OnWindows

and

i ran the command below:


%HADOOP_PREFIX%\bin\hdfs namenode -format

I can not see such output mentioned in the guide,


This command will print a number of filesystem parameters. Just look for the 
following two strings to ensure that the format command succeeded.

14/01/18 08:36:23 INFO namenode.FSImage: Saving image file 
\tmp\hadoop-username\dfs\name\current\fsimage.ckpt_0000000000000000000 using no 
compression
14/01/18 08:36:23 INFO namenode.FSImage: Image file 
\tmp\hadoop-username\dfs\name\current\fsimage.ckpt_0000000000000000000 of size 
200 bytes saved in 0 seconds.

I can see the output as below;

************************************************************/
15/09/28 10:57:00 INFO namenode.NameNode: createNameNode [-format]
Formatting using clusterid: CID-dc3dfaa8-663b-46bb-8529-14f7ffaa0522
15/09/28 10:57:01 INFO namenode.FSNamesystem: No KeyProvider found.
15/09/28 10:57:01 INFO namenode.FSNamesystem: fsLock is fair:true
15/09/28 10:57:01 INFO blockmanagement.DatanodeManager: dfs.block.invalidate.lim
it=1000
15/09/28 10:57:01 INFO blockmanagement.DatanodeManager: 
dfs.namenode.datanode.re<http://dfs.namenode.datanode.re>
gistration.ip-hostname-check=true
15/09/28 10:57:01 INFO blockmanagement.BlockManager: dfs.namenode.startup.delay.
block.deletion.sec is set to 000:00:00:00.000
15/09/28 10:57:01 INFO blockmanagement.BlockManager: The block deletion will sta
rt around 2015 Eyl 28 10:57:01
15/09/28 10:57:01 INFO util.GSet: Computing capacity for map BlocksMap
15/09/28 10:57:01 INFO util.GSet: VM type       = 64-bit
15/09/28 10:57:01 INFO util.GSet: 2.0% max memory 889 MB = 17.8 MB
15/09/28 10:57:01 INFO util.GSet: capacity      = 2^21 = 2097152 entries
15/09/28 10:57:01 INFO blockmanagement.BlockManager: dfs.block.access.token.enab
le=false
15/09/28 10:57:01 INFO blockmanagement.BlockManager: defaultReplication
= 1
15/09/28 10:57:01 INFO blockmanagement.BlockManager: maxReplication
= 512
15/09/28 10:57:01 INFO blockmanagement.BlockManager: minReplication
= 1
15/09/28 10:57:01 INFO blockmanagement.BlockManager: maxReplicationStreams
= 2
15/09/28 10:57:01 INFO blockmanagement.BlockManager: shouldCheckForEnoughRacks
= false
15/09/28 10:57:01 INFO blockmanagement.BlockManager: replicationRecheckInterval
= 3000
15/09/28 10:57:01 INFO blockmanagement.BlockManager: encryptDataTransfer
= false
15/09/28 10:57:01 INFO blockmanagement.BlockManager: maxNumBlocksToLog
= 1000
15/09/28 10:57:01 INFO namenode.FSNamesystem: fsOwner             = <MYUSER> (a
uth:SIMPLE)
15/09/28 10:57:01 INFO namenode.FSNamesystem: supergroup          = supergroup
15/09/28 10:57:01 INFO namenode.FSNamesystem: isPermissionEnabled = true
15/09/28 10:57:01 INFO namenode.FSNamesystem: HA Enabled: false
15/09/28 10:57:01 INFO namenode.FSNamesystem: Append Enabled: true
15/09/28 10:57:02 INFO util.GSet: Computing capacity for map INodeMap
15/09/28 10:57:02 INFO util.GSet: VM type       = 64-bit
15/09/28 10:57:02 INFO util.GSet: 1.0% max memory 889 MB = 8.9 MB
15/09/28 10:57:02 INFO util.GSet: capacity      = 2^20 = 1048576 entries
15/09/28 10:57:02 INFO namenode.NameNode: Caching file names occuring more than
10 times
15/09/28 10:57:02 INFO util.GSet: Computing capacity for map cachedBlocks
15/09/28 10:57:02 INFO util.GSet: VM type       = 64-bit
15/09/28 10:57:02 INFO util.GSet: 0.25% max memory 889 MB = 2.2 MB
15/09/28 10:57:02 INFO util.GSet: capacity      = 2^18 = 262144 entries
15/09/28 10:57:02 INFO namenode.FSNamesystem: dfs.namenode.safemode.threshold-pc
t = 0.9990000128746033
15/09/28 10:57:02 INFO namenode.FSNamesystem: dfs.namenode.safemode.min.datanode
s = 0
15/09/28 10:57:02 INFO namenode.FSNamesystem: dfs.namenode.safemode.extension
  = 30000
15/09/28 10:57:02 INFO namenode.FSNamesystem: Retry cache on namenode is enabled

15/09/28 10:57:02 INFO namenode.FSNamesystem: Retry cache will use 0.03 of total
 heap and retry cache entry expiry time is 600000 millis
15/09/28 10:57:02 INFO util.GSet: Computing capacity for map NameNodeRetryCache
15/09/28 10:57:02 INFO util.GSet: VM type       = 64-bit
15/09/28 10:57:02 INFO util.GSet: 0.029999999329447746% max memory 889 MB = 273.
1 KB
15/09/28 10:57:02 INFO util.GSet: capacity      = 2^15 = 32768 entries
15/09/28 10:57:02 INFO namenode.NNConf: ACLs enabled? false
15/09/28 10:57:02 INFO namenode.NNConf: XAttrs enabled? true
15/09/28 10:57:02 INFO namenode.NNConf: Maximum size of an xattr: 16384
15/09/28 10:57:02 INFO namenode.FSImage: Allocated new BlockPoolId: BP-635746082
-10.252.163.111-1443427022202
15/09/28 10:57:02 INFO common.Storage: Storage directory \tmp\hadoop-<MYUSER>\d
fs\name has been successfully formatted.
15/09/28 10:57:02 INFO namenode.NNStorageRetentionManager: Going to retain 1 ima
ges with txid >= 0
15/09/28 10:57:02 INFO util.ExitUtil: Exiting with status 0
15/09/28 10:57:02 INFO namenode.NameNode: SHUTDOWN_MSG:
/************************************************************
SHUTDOWN_MSG: Shutting down NameNode at .....
************************************************************/

I am not sure if everything is OK or not?

and i left like the values are low;

15/09/28 10:57:01 INFO util.GSet: Computing capacity for map BlocksMap
15/09/28 10:57:01 INFO util.GSet: VM type       = 64-bit
15/09/28 10:57:01 INFO util.GSet: 2.0% max memory 889 MB = 17.8 MB
15/09/28 10:57:01 INFO util.GSet: capacity      = 2^21 = 2097152 entries


Could anyone help me understand if these values are ok?

Cheers

--
Regards
Onder

Reply via email to