Wei-Chiu Chuang created HDFS-12249:
--------------------------------------
Summary: dfsadmin -metaSave to output maintenance mode blocks
Key: HDFS-12249
URL: https://issues.apache.org/jira/browse/HDFS-12249
Project: Hadoop HDFS
Issue Type: Bug
Components: namenode
Reporter: Wei-Chiu Chuang
Assignee: Wellington Chevreuil
Priority: Minor
Found while reviewing for HDFS-12182.
{quote}
After the patch, the output of metaSave is:
Live Datanodes: 0
Dead Datanodes: 0
Metasave: Blocks waiting for reconstruction: 0
Metasave: Blocks currently missing: 1
file16387: blk_0_1 MISSING (replicas: l: 0 d: 0 c: 2 e: 0)
1.1.1.1:9866(corrupt) (block deletions maybe out of date) :
2.2.2.2:9866(corrupt) (block deletions maybe out of date) :
Mis-replicated blocks that have been postponed:
Metasave: Blocks being reconstructed: 0
Metasave: Blocks 0 waiting deletion from 0 datanodes.
Corrupt Blocks:
Block=0 Node=1.1.1.1:9866 StorageID=s1 StorageState=NORMAL
TotalReplicas=2 Reason=GENSTAMP_MISMATCH
Block=0 Node=2.2.2.2:9866 StorageID=s2 StorageState=NORMAL
TotalReplicas=2 Reason=GENSTAMP_MISMATCH
Metasave: Number of datanodes: 0
{quote}
{quote}
Looking at the output
The output is not user friendly — The meaning of "(replicas: l: 0 d: 0 c: 2 e:
0)" is not obvious without looking at the code.
Also, it should print maintenance mode replicas.
{quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
