[jira] [Commented] (HDFS-15629) Add seqno when warning slow mirror/disk in BlockReceiver
[ https://issues.apache.org/jira/browse/HDFS-15629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17216451#comment-17216451 ] Ayush Saxena commented on HDFS-15629: - Committed to trunk. Thanx [~huanghaibin] for the contribution!!! > Add seqno when warning slow mirror/disk in BlockReceiver > > > Key: HDFS-15629 > URL: https://issues.apache.org/jira/browse/HDFS-15629 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Haibin Huang >Assignee: Haibin Huang >Priority: Major > Attachments: HDFS-15629-001.patch > > > When client write slow, it will print a slow log from DataStreamer > {code:java} > if (ack.getSeqno() != DFSPacket.HEART_BEAT_SEQNO) { > Long begin = packetSendTime.get(ack.getSeqno()); > if (begin != null) { > long duration = Time.monotonicNow() - begin; > if (duration > dfsclientSlowLogThresholdMs) { > LOG.info("Slow ReadProcessor read fields for block " + block > + " took " + duration + "ms (threshold=" > + dfsclientSlowLogThresholdMs + "ms); ack: " + ack > + ", targets: " + Arrays.asList(targets)); > } > } > } > {code} > here is an example: > Slow ReadProcessor read fields for block BP-XXX:blk_XXX took 2756ms > (threshold=100ms); ack: seqno: 3341 status: SUCCESS status: SUCCESS status: > SUCCESS downstreamAckTimeNanos: 2751531959 4: "\000\000\000", targets: [XXX, > XXX, XXX] > There is an ack seqno in the log, so we can find which packet cause write > slow. However, datanode didn't print the seqno in slow log, so we can't kown > this packet write slow in which stage. > HDFS-11603 and HDFS-12814 add some slow warnings in BlockReceiver, i think we > should add seqno in these slow warnings, in order to find the corresponding > packet write slow in which stage. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-15629) Add seqno when warning slow mirror/disk in BlockReceiver
[ https://issues.apache.org/jira/browse/HDFS-15629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17215807#comment-17215807 ] Ayush Saxena commented on HDFS-15629: - v001 LGTM +1, Will commit by EOD > Add seqno when warning slow mirror/disk in BlockReceiver > > > Key: HDFS-15629 > URL: https://issues.apache.org/jira/browse/HDFS-15629 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Haibin Huang >Assignee: Haibin Huang >Priority: Major > Attachments: HDFS-15629-001.patch > > > When client write slow, it will print a slow log from DataStreamer > {code:java} > if (ack.getSeqno() != DFSPacket.HEART_BEAT_SEQNO) { > Long begin = packetSendTime.get(ack.getSeqno()); > if (begin != null) { > long duration = Time.monotonicNow() - begin; > if (duration > dfsclientSlowLogThresholdMs) { > LOG.info("Slow ReadProcessor read fields for block " + block > + " took " + duration + "ms (threshold=" > + dfsclientSlowLogThresholdMs + "ms); ack: " + ack > + ", targets: " + Arrays.asList(targets)); > } > } > } > {code} > here is an example: > Slow ReadProcessor read fields for block BP-XXX:blk_XXX took 2756ms > (threshold=100ms); ack: seqno: 3341 status: SUCCESS status: SUCCESS status: > SUCCESS downstreamAckTimeNanos: 2751531959 4: "\000\000\000", targets: [XXX, > XXX, XXX] > There is an ack seqno in the log, so we can find which packet cause write > slow. However, datanode didn't print the seqno in slow log, so we can't kown > this packet write slow in which stage. > HDFS-11603 and HDFS-12814 add some slow warnings in BlockReceiver, i think we > should add seqno in these slow warnings, in order to find the corresponding > packet write slow in which stage. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-15629) Add seqno when warning slow mirror/disk in BlockReceiver
[ https://issues.apache.org/jira/browse/HDFS-15629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17213097#comment-17213097 ] Hadoop QA commented on HDFS-15629: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Logfile || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 52s{color} | | {color:blue} Docker mode activated. {color} | || || || || {color:brown} Prechecks {color} || || | {color:green}+1{color} | {color:green} dupname {color} | {color:green} 0m 0s{color} | | {color:green} No case conflicting files found. {color} | | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s{color} | | {color:green} The patch does not contain any @author tags. {color} | | {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s{color} | | {color:red} The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color} | || || || || {color:brown} trunk Compile Tests {color} || || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 20m 57s{color} | | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 18s{color} | | {color:green} trunk passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 9s{color} | | {color:green} trunk passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01 {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 47s{color} | | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m 17s{color} | | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 15m 51s{color} | | {color:green} branch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 52s{color} | | {color:green} trunk passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 24s{color} | | {color:green} trunk passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01 {color} | | {color:blue}0{color} | {color:blue} spotbugs {color} | {color:blue} 3m 1s{color} | | {color:blue} Used deprecated FindBugs config; considering switching to SpotBugs. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m 58s{color} | | {color:green} trunk passed {color} | || || || || {color:brown} Patch Compile Tests {color} || || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m 8s{color} | | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 9s{color} | | {color:green} the patch passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m 9s{color} | | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 2s{color} | | {color:green} the patch passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01 {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m 2s{color} | | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} blanks {color} | {color:green} 0m 0s{color} | | {color:green} The patch has no blanks issues. {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 39s{color} | | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m 10s{color} | | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 16m 47s{color} | | {color:green} patch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 46s{color} | | {color:green} the patch passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 21s{color} | | {color:green} the patch passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01 {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m 59s{color} | | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || || | {color:red}-1{color} | {color:red} unit {color} | {color:red}102m 38s{color} |