[
https://issues.apache.org/jira/browse/HDFS-7674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14512365#comment-14512365
]
Walter Su commented on HDFS-7674:
---------------------------------
*TODO*: Separate EC need-to-Recover blockGoup counting from under-replicated
block counting.
Description:
HDFS-7912 include EC recovery blockGroup into {{UnderReplicatedBlocks}}.
When user run
{code}
# dfsadmin -report
Configured Capacity: 786329370624 (732.33 GB)
Present Capacity: 706469978112 (657.95 GB)
DFS Remaining: 706207547392 (657.71 GB)
DFS Used: 262430720 (250.27 MB)
DFS Used%: 0.04%
Under replicated blocks: 3
...
{code}
We should separate EC need-to-Recover blockGoup counting from under-replicated
block counting.
Same as NN WebUI.
> Adding metrics for Erasure Coding
> ---------------------------------
>
> Key: HDFS-7674
> URL: https://issues.apache.org/jira/browse/HDFS-7674
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Kai Zheng
> Assignee: Wei Zhou
>
> As the design (in HDFS-7285) indicates, erasure coding involves non-trivial
> impact and workload for NameNode, DataNode and client; it also allows
> configurable and pluggable erasure codec and schema with flexible tradeoff
> options (see HDFS-7337). To support necessary analysis and adjustment, we'd
> better have various meaningful metrics for the EC support, like
> encoding/decoding tasks, recovered blocks, read/transferred data size,
> computation time and etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
