[
https://issues.apache.org/jira/browse/HDFS-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaoyu Yao updated HDFS-4169:
-----------------------------
Description: Currently, if one of the drives on the DataNode is slow, it's
hard to determine what the issue is. This can happen due to a failing disk, bad
controller, etc. It would be preferable to expose per-drive metrics/jmx with
latency statistics about how long reads/writes are taking. (was: Currently, if
one of the drives on the DataNode is slow, it's hard to determine what the
issue is. This can happen due to a failing disk, bad controller, etc. It would
be preferable to expose per-drive MXBeans (or tagged metrics) with latency
statistics about how long reads/writes are taking.)
> Add per-disk latency metrics to DataNode
> ----------------------------------------
>
> Key: HDFS-4169
> URL: https://issues.apache.org/jira/browse/HDFS-4169
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode
> Affects Versions: 3.0.0-alpha1
> Reporter: Todd Lipcon
> Assignee: Xiaoyu Yao
>
> Currently, if one of the drives on the DataNode is slow, it's hard to
> determine what the issue is. This can happen due to a failing disk, bad
> controller, etc. It would be preferable to expose per-drive metrics/jmx with
> latency statistics about how long reads/writes are taking.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
