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

Yiqun Lin commented on HDFS-11371:
----------------------------------

Hi [~andrew.wang], I found some metrics relevant EC that are added in 
3.0.0-alpha2(HDFS-8411 and HDFS-11216 done for this), but they haven't been 
documented yet. We can have a fix in 3.0.0-alpha3. Are you interest in taking a 
quick look for this? This is a minor change.

> Document missing metrics of erasure coding
> ------------------------------------------
>
>                 Key: HDFS-11371
>                 URL: https://issues.apache.org/jira/browse/HDFS-11371
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: documentation, erasure-coding
>    Affects Versions: 3.0.0-alpha2
>            Reporter: Yiqun Lin
>            Assignee: Yiqun Lin
>            Priority: Minor
>         Attachments: HDFS-11371.001.patch
>
>
> HDFS-8411, HDFS-11216 add some metrics of erasure coding, but it hasn't been 
> documented. The following metrics in {{DataNodeMetrics}} is missing in 
> documentation.
> {code}
>   @Metric("Count of erasure coding reconstruction tasks")
>   MutableCounterLong ecReconstructionTasks;
>   @Metric("Count of erasure coding failed reconstruction tasks")
>   MutableCounterLong ecFailedReconstructionTasks;
>   @Metric("Nanoseconds spent by decoding tasks")
>   MutableCounterLong ecDecodingTimeNanos;
>   @Metric("Bytes read by erasure coding worker")
>   MutableCounterLong ecReconstructionBytesRead;
>   @Metric("Bytes written by erasure coding worker")
>   MutableCounterLong ecReconstructionBytesWritten;
>   @Metric("Bytes remote read by erasure coding worker")
>   MutableCounterLong ecReconstructionRemoteBytesRead;
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to