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 "Xiao Chen (JIRA)" <ji...@apache.org> on 2017/01/25 02:24:26 UTC

[jira] [Updated] (HDFS-11363) Need more diagnosis info when seeing Slow waitForAckedSeqno

     [ https://issues.apache.org/jira/browse/HDFS-11363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xiao Chen updated HDFS-11363:
-----------------------------
    Attachment: HDFS-11363.01.patch

Attaching patch 1 for the logs.
Added filename, block, and datanode list to the message. A sample output looks like:

{noformat}
2017-01-24 18:15:02,402 WARN hdfs.DataStreamer: Slow waitForAckedSeqno took 144ms (threshold=30000ms). 
File: /dir/f._COPYING_, block: BP-1326647282-172.16.3.121-1485309974936:blk_1073741825_1001, 
datanodes: [DatanodeInfoWithStorage[127.0.0.1:8765,DS-f00ca0c5-5cfe-41d1-910f-c0494a50334d,DISK]]
{noformat}

[~yzhangal], is this what you had in mind? Thanks.

> Need more diagnosis info when seeing Slow waitForAckedSeqno
> -----------------------------------------------------------
>
>                 Key: HDFS-11363
>                 URL: https://issues.apache.org/jira/browse/HDFS-11363
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Yongjun Zhang
>            Assignee: Xiao Chen
>         Attachments: HDFS-11363.01.patch
>
>
> When client writes a file, it may get the following message when ACK doesn't get back in a timely manner:
> WARN hdfs.DFSClient: Slow waitForAckedSeqno took 39264ms (threshold=30000ms)
> It would be nice to tell what file it's writing, and what DataNodes are in the pipeline, together with this message, to facilitate investigating related performance issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org