hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wellington Chevreuil (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12249) dfsadmin -metaSave to output maintenance mode blocks
Date Wed, 02 Aug 2017 20:27:00 GMT

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

Wellington Chevreuil commented on HDFS-12249:
---------------------------------------------

Thanks for the insights, [~jojochuang]! Just to confirm on the expectations here, once a node
goes into maintenance, its replicas would be listed under "Blocks waiting for reconstruction"
section?

Here is a sample output after some initial changes, for a block with 2 replicas, one of the
replicas on a node under maintenance:

{noformat}
Live Datanodes: 0
Dead Datanodes: 0
Metasave: Blocks waiting for reconstruction: 1
file16387: blk_0_0 (replicas: live: 1 decommissioned: 0 corrupt: 0 in excess: 0 maintenance
mode: 1)  1.1.1.1:9866(maintenance) (block deletions maybe out of date) :  2.2.2.2:9866 (block
deletions maybe out of date) :
Metasave: Blocks currently missing: 0
Mis-replicated blocks that have been postponed:
Metasave: Blocks being reconstructed: 0
Metasave: Blocks 0 waiting deletion from 0 datanodes.
Corrupt Blocks:
Metasave: Number of datanodes: 0

{noformat}

> 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-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message