[ https://issues.apache.org/jira/browse/HDFS-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14014412#comment-14014412 ]
Hudson commented on HDFS-6110: ------------------------------ SUCCESS: Integrated in Hadoop-trunk-Commit #5638 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/5638/]) Move HDFS-6110 down to 2.5.0 section of CHANGES.txt (wang: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1598787) * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt > 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)