You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "stack (JIRA)" <ji...@apache.org> on 2014/05/26 21:49:01 UTC
[jira] [Updated] (HDFS-6110) adding more slow action log in
critical write path
[ https://issues.apache.org/jira/browse/HDFS-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HDFS-6110:
------------------------
Resolution: Fixed
Fix Version/s: 2.5.0
Release Note:
Log slow i/o. Set log thresholds in dfsclient and datanode via the below new configs:
dfs.client.slow.io.warning.threshold.ms (Default 30 seconds)
dfs.datanode.slow.io.warning.threshold.ms (Default 300ms)
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2. Thanks for the patch Liang Xie.
> 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
> 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
(v6.2#6252)