[
https://issues.apache.org/jira/browse/HDFS-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HDFS-6110:
------------------------
Attachment: HDFS-6110v3.txt
I tried it out. Looks good. Minor formatting of log changes (They all have a
'Slow' prefix...). Here is an example:
{code}
2014-03-27 22:46:19,975 WARN org.apache.hadoop.hdfs.server.datanode.DataNode:
Slow BlockReceiver write packet to mirror took 986ms (threshold=300ms)
{code}
Was going to commit with the conservative 300ms threshold unless objection.
> adding more slow action log in critical write path
> --------------------------------------------------
>
> Key: HDFS-6110
> URL: https://issues.apache.org/jira/browse/HDFS-6110
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode
> Affects Versions: 3.0.0, 2.3.0
> Reporter: Liang Xie
> Assignee: Liang Xie
> Attachments: HDFS-6110-v2.txt, HDFS-6110.txt, HDFS-6110v3.txt
>
>
> After digging a HBase write spike issue caused by slow buffer io in our
> cluster, just realize we'd better to add more abnormal latency warning log in
> write flow, such that if other guys hit HLog sync spike, we could know more
> detail info from HDFS side at the same time.
> Patch will be uploaded soon.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
