[jira] [Commented] (HDFS-10960) TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails at disk error verification after volume remove
[ https://issues.apache.org/jira/browse/HDFS-10960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576649#comment-15576649 ] Manoj Govindassamy commented on HDFS-10960: --- Tested 01 patch on both branch2 and branch2.8 and they are build good and test passes through. > TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails at disk error > verification after volume remove > > > Key: HDFS-10960 > URL: https://issues.apache.org/jira/browse/HDFS-10960 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 3.0.0-alpha2 >Reporter: Manoj Govindassamy >Assignee: Manoj Govindassamy >Priority: Minor > Fix For: 2.8.0, 2.9.0, 3.0.0-alpha2 > > Attachments: HDFS-10960.01.patch, HDFS-10960.02.patch > > > TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails occasionally in > the following verification. > {code} > 700 // If an IOException thrown from BlockReceiver#run, it triggers > 701 // DataNode#checkDiskError(). So we can test whether > checkDiskError() is called, > 702 // to see whether there is IOException in BlockReceiver#run(). > 703 assertEquals(lastTimeDiskErrorCheck, dn.getLastDiskErrorCheck()); > 704 > {code} > {noformat} > Error Message > expected:<0> but was:<6498109> > Stacktrace > java.lang.AssertionError: expected:<0> but was:<6498109> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at > org.apache.hadoop.hdfs.server.datanode.TestDataNodeHotSwapVolumes.testRemoveVolumeBeingWrittenForDatanode(TestDataNodeHotSwapVolumes.java:703) > at > org.apache.hadoop.hdfs.server.datanode.TestDataNodeHotSwapVolumes.testRemoveVolumeBeingWritten(TestDataNodeHotSwapVolumes.java:620) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-10960) TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails at disk error verification after volume remove
[ https://issues.apache.org/jira/browse/HDFS-10960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576581#comment-15576581 ] Manoj Govindassamy commented on HDFS-10960: --- [~eddyxu]. v01 patch should work there as it uses getBasePath() instead of getBaseURI(). > TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails at disk error > verification after volume remove > > > Key: HDFS-10960 > URL: https://issues.apache.org/jira/browse/HDFS-10960 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 3.0.0-alpha2 >Reporter: Manoj Govindassamy >Assignee: Manoj Govindassamy >Priority: Minor > Fix For: 2.8.0, 2.9.0, 3.0.0-alpha2 > > Attachments: HDFS-10960.01.patch, HDFS-10960.02.patch > > > TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails occasionally in > the following verification. > {code} > 700 // If an IOException thrown from BlockReceiver#run, it triggers > 701 // DataNode#checkDiskError(). So we can test whether > checkDiskError() is called, > 702 // to see whether there is IOException in BlockReceiver#run(). > 703 assertEquals(lastTimeDiskErrorCheck, dn.getLastDiskErrorCheck()); > 704 > {code} > {noformat} > Error Message > expected:<0> but was:<6498109> > Stacktrace > java.lang.AssertionError: expected:<0> but was:<6498109> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at > org.apache.hadoop.hdfs.server.datanode.TestDataNodeHotSwapVolumes.testRemoveVolumeBeingWrittenForDatanode(TestDataNodeHotSwapVolumes.java:703) > at > org.apache.hadoop.hdfs.server.datanode.TestDataNodeHotSwapVolumes.testRemoveVolumeBeingWritten(TestDataNodeHotSwapVolumes.java:620) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-10960) TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails at disk error verification after volume remove
[ https://issues.apache.org/jira/browse/HDFS-10960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576575#comment-15576575 ] Lei (Eddy) Xu commented on HDFS-10960: -- hi, [~kihwal] Thanks for reporting it. Working on fixing it now. > TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails at disk error > verification after volume remove > > > Key: HDFS-10960 > URL: https://issues.apache.org/jira/browse/HDFS-10960 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 3.0.0-alpha2 >Reporter: Manoj Govindassamy >Assignee: Manoj Govindassamy >Priority: Minor > Fix For: 2.8.0, 2.9.0, 3.0.0-alpha2 > > Attachments: HDFS-10960.01.patch, HDFS-10960.02.patch > > > TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails occasionally in > the following verification. > {code} > 700 // If an IOException thrown from BlockReceiver#run, it triggers > 701 // DataNode#checkDiskError(). So we can test whether > checkDiskError() is called, > 702 // to see whether there is IOException in BlockReceiver#run(). > 703 assertEquals(lastTimeDiskErrorCheck, dn.getLastDiskErrorCheck()); > 704 > {code} > {noformat} > Error Message > expected:<0> but was:<6498109> > Stacktrace > java.lang.AssertionError: expected:<0> but was:<6498109> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at > org.apache.hadoop.hdfs.server.datanode.TestDataNodeHotSwapVolumes.testRemoveVolumeBeingWrittenForDatanode(TestDataNodeHotSwapVolumes.java:703) > at > org.apache.hadoop.hdfs.server.datanode.TestDataNodeHotSwapVolumes.testRemoveVolumeBeingWritten(TestDataNodeHotSwapVolumes.java:620) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-10960) TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails at disk error verification after volume remove
[ https://issues.apache.org/jira/browse/HDFS-10960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576572#comment-15576572 ] Kihwal Lee commented on HDFS-10960: --- Reverted from branch-2 and branch-2.8. Please rework the patch for these branches. > TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails at disk error > verification after volume remove > > > Key: HDFS-10960 > URL: https://issues.apache.org/jira/browse/HDFS-10960 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 3.0.0-alpha2 >Reporter: Manoj Govindassamy >Assignee: Manoj Govindassamy >Priority: Minor > Fix For: 2.8.0, 2.9.0, 3.0.0-alpha2 > > Attachments: HDFS-10960.01.patch, HDFS-10960.02.patch > > > TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails occasionally in > the following verification. > {code} > 700 // If an IOException thrown from BlockReceiver#run, it triggers > 701 // DataNode#checkDiskError(). So we can test whether > checkDiskError() is called, > 702 // to see whether there is IOException in BlockReceiver#run(). > 703 assertEquals(lastTimeDiskErrorCheck, dn.getLastDiskErrorCheck()); > 704 > {code} > {noformat} > Error Message > expected:<0> but was:<6498109> > Stacktrace > java.lang.AssertionError: expected:<0> but was:<6498109> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at > org.apache.hadoop.hdfs.server.datanode.TestDataNodeHotSwapVolumes.testRemoveVolumeBeingWrittenForDatanode(TestDataNodeHotSwapVolumes.java:703) > at > org.apache.hadoop.hdfs.server.datanode.TestDataNodeHotSwapVolumes.testRemoveVolumeBeingWritten(TestDataNodeHotSwapVolumes.java:620) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-10960) TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails at disk error verification after volume remove
[ https://issues.apache.org/jira/browse/HDFS-10960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576561#comment-15576561 ] Kihwal Lee commented on HDFS-10960: --- branch-2 build fails. {noformat} [ERROR] /home1/kihwal/devel/apache/hadoop/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/datanode/TestDataNodeHotSwapVolumes.java:[710,38] cannot find symbol [ERROR] symbol: method getBaseURI() [ERROR] location: interface org.apache.hadoop.hdfs.server.datanode.fsdataset.FsVolumeSpi {noformat} > TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails at disk error > verification after volume remove > > > Key: HDFS-10960 > URL: https://issues.apache.org/jira/browse/HDFS-10960 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 3.0.0-alpha2 >Reporter: Manoj Govindassamy >Assignee: Manoj Govindassamy >Priority: Minor > Fix For: 2.8.0, 2.9.0, 3.0.0-alpha2 > > Attachments: HDFS-10960.01.patch, HDFS-10960.02.patch > > > TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails occasionally in > the following verification. > {code} > 700 // If an IOException thrown from BlockReceiver#run, it triggers > 701 // DataNode#checkDiskError(). So we can test whether > checkDiskError() is called, > 702 // to see whether there is IOException in BlockReceiver#run(). > 703 assertEquals(lastTimeDiskErrorCheck, dn.getLastDiskErrorCheck()); > 704 > {code} > {noformat} > Error Message > expected:<0> but was:<6498109> > Stacktrace > java.lang.AssertionError: expected:<0> but was:<6498109> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at > org.apache.hadoop.hdfs.server.datanode.TestDataNodeHotSwapVolumes.testRemoveVolumeBeingWrittenForDatanode(TestDataNodeHotSwapVolumes.java:703) > at > org.apache.hadoop.hdfs.server.datanode.TestDataNodeHotSwapVolumes.testRemoveVolumeBeingWritten(TestDataNodeHotSwapVolumes.java:620) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-10960) TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails at disk error verification after volume remove
[ https://issues.apache.org/jira/browse/HDFS-10960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576466#comment-15576466 ] Hudson commented on HDFS-10960: --- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10615 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/10615/]) HDFS-10960. TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten (lei: rev 8c520a27cbd9daba05367d3a83017a2eab5258eb) * (edit) hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/datanode/TestDataNodeHotSwapVolumes.java > TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails at disk error > verification after volume remove > > > Key: HDFS-10960 > URL: https://issues.apache.org/jira/browse/HDFS-10960 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 3.0.0-alpha2 >Reporter: Manoj Govindassamy >Assignee: Manoj Govindassamy >Priority: Minor > Fix For: 2.8.0, 2.9.0, 3.0.0-alpha2 > > Attachments: HDFS-10960.01.patch, HDFS-10960.02.patch > > > TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails occasionally in > the following verification. > {code} > 700 // If an IOException thrown from BlockReceiver#run, it triggers > 701 // DataNode#checkDiskError(). So we can test whether > checkDiskError() is called, > 702 // to see whether there is IOException in BlockReceiver#run(). > 703 assertEquals(lastTimeDiskErrorCheck, dn.getLastDiskErrorCheck()); > 704 > {code} > {noformat} > Error Message > expected:<0> but was:<6498109> > Stacktrace > java.lang.AssertionError: expected:<0> but was:<6498109> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at > org.apache.hadoop.hdfs.server.datanode.TestDataNodeHotSwapVolumes.testRemoveVolumeBeingWrittenForDatanode(TestDataNodeHotSwapVolumes.java:703) > at > org.apache.hadoop.hdfs.server.datanode.TestDataNodeHotSwapVolumes.testRemoveVolumeBeingWritten(TestDataNodeHotSwapVolumes.java:620) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-10960) TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails at disk error verification after volume remove
[ https://issues.apache.org/jira/browse/HDFS-10960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576268#comment-15576268 ] Hadoop QA commented on HDFS-10960: -- | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 15s{color} | {color:blue} Docker mode activated. {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:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 0s{color} | {color:green} The patch appears to include 1 new or modified test files. {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 8m 4s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 59s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 30s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m 8s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 13s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m 1s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 44s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 45s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 43s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 43s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 23s{color} | {color:green} hadoop-hdfs-project/hadoop-hdfs: The patch generated 0 new + 14 unchanged - 1 fixed = 14 total (was 15) {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 49s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 9s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 51s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 37s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} unit {color} | {color:green} 60m 36s{color} | {color:green} hadoop-hdfs in the patch passed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 19s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black} 81m 18s{color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Docker | Image:yetus/hadoop:9560f25 | | JIRA Issue | HDFS-10960 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12833422/HDFS-10960.02.patch | | Optional Tests | asflicense compile javac javadoc mvninstall mvnsite unit findbugs checkstyle | | uname | Linux 3f5d823996bd 3.13.0-95-generic #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | /testptch/hadoop/patchprocess/precommit/personality/provided.sh | | git revision | trunk / 701c27a | | Default Java | 1.8.0_101 | | findbugs | v3.0.0 | | Test Results | https://builds.apache.org/job/PreCommit-HDFS-Build/17163/testReport/ | | modules | C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs | | Console output | https://builds.apache.org/job/PreCommit-HDFS-Build/17163/console | | Powered by | Apache Yetus 0.4.0-SNAPSHOT http://yetus.apache.org | This message was automatically generated. > TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails at disk error > verification after volume remove > > > Key: HDFS-10960 > URL: https://issues.apache.org/jira/browse/HDFS-10960 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 3.0.0-alpha2 >Reporter: Manoj Govindassamy >Assignee: Manoj Govindassamy >
[jira] [Commented] (HDFS-10960) TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails at disk error verification after volume remove
[ https://issues.apache.org/jira/browse/HDFS-10960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15573338#comment-15573338 ] Lei (Eddy) Xu commented on HDFS-10960: -- Hi, [~manojg] The patch fails to build on the newest trunk. You might need to rebase it. Beside that, +1 pending. It is a nice fix. Thanks! > TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails at disk error > verification after volume remove > > > Key: HDFS-10960 > URL: https://issues.apache.org/jira/browse/HDFS-10960 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 3.0.0-alpha2 >Reporter: Manoj Govindassamy >Assignee: Manoj Govindassamy >Priority: Minor > Attachments: HDFS-10960.01.patch > > > TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails occasionally in > the following verification. > {code} > 700 // If an IOException thrown from BlockReceiver#run, it triggers > 701 // DataNode#checkDiskError(). So we can test whether > checkDiskError() is called, > 702 // to see whether there is IOException in BlockReceiver#run(). > 703 assertEquals(lastTimeDiskErrorCheck, dn.getLastDiskErrorCheck()); > 704 > {code} > {noformat} > Error Message > expected:<0> but was:<6498109> > Stacktrace > java.lang.AssertionError: expected:<0> but was:<6498109> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at > org.apache.hadoop.hdfs.server.datanode.TestDataNodeHotSwapVolumes.testRemoveVolumeBeingWrittenForDatanode(TestDataNodeHotSwapVolumes.java:703) > at > org.apache.hadoop.hdfs.server.datanode.TestDataNodeHotSwapVolumes.testRemoveVolumeBeingWritten(TestDataNodeHotSwapVolumes.java:620) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-10960) TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails at disk error verification after volume remove
[ https://issues.apache.org/jira/browse/HDFS-10960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15547035#comment-15547035 ] Hadoop QA commented on HDFS-10960: -- | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 14s{color} | {color:blue} Docker mode activated. {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:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 0s{color} | {color:green} The patch appears to include 1 new or modified test files. {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m 13s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 47s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 26s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 54s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 12s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 43s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 55s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 53s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 44s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 44s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 23s{color} | {color:green} hadoop-hdfs-project/hadoop-hdfs: The patch generated 0 new + 14 unchanged - 1 fixed = 14 total (was 15) {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 48s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 10s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 47s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 52s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} unit {color} | {color:green} 60m 57s{color} | {color:green} hadoop-hdfs in the patch passed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 19s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black} 80m 33s{color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Docker | Image:yetus/hadoop:9560f25 | | JIRA Issue | HDFS-10960 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12831625/HDFS-10960.01.patch | | Optional Tests | asflicense compile javac javadoc mvninstall mvnsite unit findbugs checkstyle | | uname | Linux 04c963d09245 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | /testptch/hadoop/patchprocess/precommit/personality/provided.sh | | git revision | trunk / 44f48ee | | Default Java | 1.8.0_101 | | findbugs | v3.0.0 | | Test Results | https://builds.apache.org/job/PreCommit-HDFS-Build/17008/testReport/ | | modules | C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs | | Console output | https://builds.apache.org/job/PreCommit-HDFS-Build/17008/console | | Powered by | Apache Yetus 0.4.0-SNAPSHOT http://yetus.apache.org | This message was automatically generated. > TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails at disk error > verification after volume remove > > > Key: HDFS-10960 > URL: https://issues.apache.org/jira/browse/HDFS-10960 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 3.0.0-alpha2 >Reporter: Manoj Govindassamy >Assignee: Manoj Govind
[jira] [Commented] (HDFS-10960) TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails at disk error verification after volume remove
[ https://issues.apache.org/jira/browse/HDFS-10960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15546654#comment-15546654 ] Manoj Govindassamy commented on HDFS-10960: --- Looking at the code, remove volumes at DataNode can potentially interrupt BlockReceiver and if the BlockReceiver happens to be in some IO operations like flushing or setting channel position for the new checksum then it can throw IOException. {{BlockReceiver}} on getting IOexception, starts a thread to check for disk errors. TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten verification fails if the DataNode ever started a disk error check thread. This verification doesn't seem to be fruitful as we already have another verification for checking the block replication factor. So, the proposal here is to replace this not so useful verification with another verification to check for if the disk removal happened successfully and if the replication factor of the block caught up even after the volume removal. > TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails at disk error > verification after volume remove > > > Key: HDFS-10960 > URL: https://issues.apache.org/jira/browse/HDFS-10960 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs >Affects Versions: 3.0.0-alpha2 >Reporter: Manoj Govindassamy >Assignee: Manoj Govindassamy >Priority: Minor > > TestDataNodeHotSwapVolumes#testRemoveVolumeBeingWritten fails occasionally in > the following verification. > {code} > 700 // If an IOException thrown from BlockReceiver#run, it triggers > 701 // DataNode#checkDiskError(). So we can test whether > checkDiskError() is called, > 702 // to see whether there is IOException in BlockReceiver#run(). > 703 assertEquals(lastTimeDiskErrorCheck, dn.getLastDiskErrorCheck()); > 704 > {code} > {noformat} > Error Message > expected:<0> but was:<6498109> > Stacktrace > java.lang.AssertionError: expected:<0> but was:<6498109> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at > org.apache.hadoop.hdfs.server.datanode.TestDataNodeHotSwapVolumes.testRemoveVolumeBeingWrittenForDatanode(TestDataNodeHotSwapVolumes.java:703) > at > org.apache.hadoop.hdfs.server.datanode.TestDataNodeHotSwapVolumes.testRemoveVolumeBeingWritten(TestDataNodeHotSwapVolumes.java:620) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org