Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
-
None
Description
Environment Cluster of 2 Namenodes and 5 Datanodes and ec policy enabled
fsck -blockId of a block associated with an EC File does not print status at the end and displays null instead
Result :
./hdfs fsck -blockId blk_-xxxxx
Connecting to namenode via xxxx
FSCK started by root (auth:SIMPLE) from /x.x.x.x at Wed Nov 13 19:37:02 CST 2019
Block Id: blk_-xxxxx
Block belongs to: /ecdir/f2
No. of Expected Replica: 3
No. of live Replica: 3
No. of excess Replica: 0
No. of stale Replica: 2
No. of decommissioned Replica: 0
No. of decommissioning Replica: 0
No. of corrupted Replica: 0
null
Expected :
./hdfs fsck -blockId blk_-xxxxx
Connecting to namenode via xxxx
FSCK started by root (auth:SIMPLE) from /x.x.x.x at Wed Nov 13 19:37:02 CST 2019
Block Id: blk_-xxxxx
Block belongs to: /ecdir/f2
No. of Expected Replica: 3
No. of live Replica: 3
No. of excess Replica: 0
No. of stale Replica: 2
No. of decommissioned Replica: 0
No. of decommissioning Replica: 0
No. of corrupted Replica: 0
Block replica on datanode/rack: vm10/default-rack is HEALTHY
Attachments
Issue Links
- is duplicated by
-
HDFS-14266 EC : Fsck -blockId shows null for EC Blocks if One Block Is Not Available.
- Resolved