[
https://issues.apache.org/jira/browse/HDFS-14985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ravuri Sushma sree updated HDFS-14985:
--------------------------------------
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
{color:#de350b}*Result :*{color}
./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
{color:#de350b}*Expected :*{color}
./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
was:
FSCK of a blockid which belongs to an EC File doesnot print status at the end
and displays null instead
./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
> FSCK for a block of EC Files doesnt display status at the end
> -------------------------------------------------------------
>
> Key: HDFS-14985
> URL: https://issues.apache.org/jira/browse/HDFS-14985
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Ravuri Sushma sree
> Assignee: Ravuri Sushma sree
> Priority: Major
>
> *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
> {color:#de350b}*Result :*{color}
> ./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
> {color:#de350b}*Expected :*{color}
> ./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
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
