[
https://issues.apache.org/jira/browse/HDFS-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16451645#comment-16451645
]
Lars Francke commented on HDFS-6110:
------------------------------------
I know this is old but in case someone else stumbles across it: This was
accidentally committed with a commit message pointing to HBASE-6110 instead.
> 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: 2.3.0, 3.0.0-alpha1
> Reporter: Liang Xie
> Assignee: Liang Xie
> Priority: Major
> Fix For: 2.5.0
>
> Attachments: HDFS-6110-v2.txt, HDFS-6110.txt, HDFS-6110v3.txt,
> HDFS-6110v4.txt, HDFS-6110v5.txt, HDFS-6110v6.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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
