[jira] [Commented] (HDFS-9358) TestNodeCount#testNodeCount timed out
[ https://issues.apache.org/jira/browse/HDFS-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15010005#comment-15010005 ] Masatake Iwasaki commented on HDFS-9358: Thanks, [~walter.k.su]! > TestNodeCount#testNodeCount timed out > - > > Key: HDFS-9358 > URL: https://issues.apache.org/jira/browse/HDFS-9358 > Project: Hadoop HDFS > Issue Type: Bug > Components: test >Reporter: Wei-Chiu Chuang >Assignee: Masatake Iwasaki > Fix For: 2.8.0 > > Attachments: HDFS-9358.001.patch, HDFS-9358.002.patch > > > I have seen this test failure occurred a few times in trunk: > Error Message > Timeout: excess replica count not equal to 2 for block blk_1073741825_1001 > after 2 msec. Last counts: live = 2, excess = 0, corrupt = 0 > Stacktrace > java.util.concurrent.TimeoutException: Timeout: excess replica count not > equal to 2 for block blk_1073741825_1001 after 2 msec. Last counts: live > = 2, excess = 0, corrupt = 0 > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:152) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:146) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.__CLR4_0_39bdgm666uf(TestNodeCount.java:130) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.testNodeCount(TestNodeCount.java:54) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-9358) TestNodeCount#testNodeCount timed out
[ https://issues.apache.org/jira/browse/HDFS-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15008273#comment-15008273 ] Hudson commented on HDFS-9358: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2548 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/2548/]) HDFS-9358. TestNodeCount#testNodeCount timed out. Contributed by (waltersu4549: rev 621cbb4f69072bde259f213629f84494416ae12f) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/blockmanagement/TestNodeCount.java > TestNodeCount#testNodeCount timed out > - > > Key: HDFS-9358 > URL: https://issues.apache.org/jira/browse/HDFS-9358 > Project: Hadoop HDFS > Issue Type: Bug > Components: test >Reporter: Wei-Chiu Chuang >Assignee: Masatake Iwasaki > Fix For: 2.8.0 > > Attachments: HDFS-9358.001.patch, HDFS-9358.002.patch > > > I have seen this test failure occurred a few times in trunk: > Error Message > Timeout: excess replica count not equal to 2 for block blk_1073741825_1001 > after 2 msec. Last counts: live = 2, excess = 0, corrupt = 0 > Stacktrace > java.util.concurrent.TimeoutException: Timeout: excess replica count not > equal to 2 for block blk_1073741825_1001 after 2 msec. Last counts: live > = 2, excess = 0, corrupt = 0 > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:152) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:146) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.__CLR4_0_39bdgm666uf(TestNodeCount.java:130) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.testNodeCount(TestNodeCount.java:54) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-9358) TestNodeCount#testNodeCount timed out
[ https://issues.apache.org/jira/browse/HDFS-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15008351#comment-15008351 ] Hudson commented on HDFS-9358: -- ABORTED: Integrated in Hadoop-Hdfs-trunk-Java8 #610 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/610/]) HDFS-9358. TestNodeCount#testNodeCount timed out. Contributed by (waltersu4549: rev 621cbb4f69072bde259f213629f84494416ae12f) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/blockmanagement/TestNodeCount.java > TestNodeCount#testNodeCount timed out > - > > Key: HDFS-9358 > URL: https://issues.apache.org/jira/browse/HDFS-9358 > Project: Hadoop HDFS > Issue Type: Bug > Components: test >Reporter: Wei-Chiu Chuang >Assignee: Masatake Iwasaki > Fix For: 2.8.0 > > Attachments: HDFS-9358.001.patch, HDFS-9358.002.patch > > > I have seen this test failure occurred a few times in trunk: > Error Message > Timeout: excess replica count not equal to 2 for block blk_1073741825_1001 > after 2 msec. Last counts: live = 2, excess = 0, corrupt = 0 > Stacktrace > java.util.concurrent.TimeoutException: Timeout: excess replica count not > equal to 2 for block blk_1073741825_1001 after 2 msec. Last counts: live > = 2, excess = 0, corrupt = 0 > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:152) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:146) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.__CLR4_0_39bdgm666uf(TestNodeCount.java:130) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.testNodeCount(TestNodeCount.java:54) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-9358) TestNodeCount#testNodeCount timed out
[
https://issues.apache.org/jira/browse/HDFS-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15007216#comment-15007216
]
Hadoop QA commented on HDFS-9358:
-
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 12s
{color} | {color:blue} docker + precommit patch detected. {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} 4m
7s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 5s
{color} | {color:green} trunk passed with JDK v1.8.0_66 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 50s
{color} | {color:green} trunk passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
19s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 52s
{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
18s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
28s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 10s
{color} | {color:green} trunk passed with JDK v1.8.0_66 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 54s
{color} | {color:green} trunk passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
2s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 48s
{color} | {color:green} the patch passed with JDK v1.8.0_66 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 48s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 38s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 38s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
18s {color} | {color:green} the patch passed {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
15s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
23s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 24s
{color} | {color:green} the patch passed with JDK v1.8.0_66 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 23s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 93m 47s {color}
| {color:red} hadoop-hdfs in the patch failed with JDK v1.8.0_66. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 86m 24s {color}
| {color:red} hadoop-hdfs in the patch failed with JDK v1.7.0_79. {color} |
| {color:red}-1{color} | {color:red} asflicense {color} | {color:red} 0m 30s
{color} | {color:red} Patch generated 56 ASF License warnings. {color} |
| {color:black}{color} | {color:black} {color} | {color:black} 209m 36s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| JDK v1.8.0_66 Failed junit tests | hadoop.hdfs.TestDFSUpgradeFromImage |
| | hadoop.hdfs.server.namenode.ha.TestEditLogTailer |
| | hadoop.hdfs.security.TestDelegationTokenForProxyUser |
| | hadoop.hdfs.server.namenode.snapshot.TestSnapshotFileLength |
| | hadoop.hdfs.server.namenode.ha.TestSeveralNameNodes |
| | hadoop.hdfs.server.namenode.ha.TestHAAppend |
| | hadoop.hdfs.TestAclsEndToEnd |
| | hadoop.hdfs.server.datanode.TestDirectoryScanner |
| JDK v1.7.0_79 Failed junit tests |
hadoop.hdfs.server.namenode.ha.TestDNFencing |
| | hadoop.hdfs.TestPersistBlocks |
| | hadoop.hdfs.TestDFSStripedOutputStreamWithFailure180 |
| |
[jira] [Commented] (HDFS-9358) TestNodeCount#testNodeCount timed out
[ https://issues.apache.org/jira/browse/HDFS-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15008014#comment-15008014 ] Hudson commented on HDFS-9358: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #671 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/671/]) HDFS-9358. TestNodeCount#testNodeCount timed out. Contributed by (waltersu4549: rev 621cbb4f69072bde259f213629f84494416ae12f) * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/blockmanagement/TestNodeCount.java * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt > TestNodeCount#testNodeCount timed out > - > > Key: HDFS-9358 > URL: https://issues.apache.org/jira/browse/HDFS-9358 > Project: Hadoop HDFS > Issue Type: Bug > Components: test >Reporter: Wei-Chiu Chuang >Assignee: Masatake Iwasaki > Fix For: 2.8.0 > > Attachments: HDFS-9358.001.patch, HDFS-9358.002.patch > > > I have seen this test failure occurred a few times in trunk: > Error Message > Timeout: excess replica count not equal to 2 for block blk_1073741825_1001 > after 2 msec. Last counts: live = 2, excess = 0, corrupt = 0 > Stacktrace > java.util.concurrent.TimeoutException: Timeout: excess replica count not > equal to 2 for block blk_1073741825_1001 after 2 msec. Last counts: live > = 2, excess = 0, corrupt = 0 > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:152) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:146) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.__CLR4_0_39bdgm666uf(TestNodeCount.java:130) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.testNodeCount(TestNodeCount.java:54) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-9358) TestNodeCount#testNodeCount timed out
[ https://issues.apache.org/jira/browse/HDFS-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15008039#comment-15008039 ] Hudson commented on HDFS-9358: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #684 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/684/]) HDFS-9358. TestNodeCount#testNodeCount timed out. Contributed by (waltersu4549: rev 621cbb4f69072bde259f213629f84494416ae12f) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/blockmanagement/TestNodeCount.java > TestNodeCount#testNodeCount timed out > - > > Key: HDFS-9358 > URL: https://issues.apache.org/jira/browse/HDFS-9358 > Project: Hadoop HDFS > Issue Type: Bug > Components: test >Reporter: Wei-Chiu Chuang >Assignee: Masatake Iwasaki > Fix For: 2.8.0 > > Attachments: HDFS-9358.001.patch, HDFS-9358.002.patch > > > I have seen this test failure occurred a few times in trunk: > Error Message > Timeout: excess replica count not equal to 2 for block blk_1073741825_1001 > after 2 msec. Last counts: live = 2, excess = 0, corrupt = 0 > Stacktrace > java.util.concurrent.TimeoutException: Timeout: excess replica count not > equal to 2 for block blk_1073741825_1001 after 2 msec. Last counts: live > = 2, excess = 0, corrupt = 0 > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:152) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:146) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.__CLR4_0_39bdgm666uf(TestNodeCount.java:130) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.testNodeCount(TestNodeCount.java:54) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-9358) TestNodeCount#testNodeCount timed out
[ https://issues.apache.org/jira/browse/HDFS-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15008057#comment-15008057 ] Hudson commented on HDFS-9358: -- FAILURE: Integrated in Hadoop-Yarn-trunk #1408 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/1408/]) HDFS-9358. TestNodeCount#testNodeCount timed out. Contributed by (waltersu4549: rev 621cbb4f69072bde259f213629f84494416ae12f) * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/blockmanagement/TestNodeCount.java * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt > TestNodeCount#testNodeCount timed out > - > > Key: HDFS-9358 > URL: https://issues.apache.org/jira/browse/HDFS-9358 > Project: Hadoop HDFS > Issue Type: Bug > Components: test >Reporter: Wei-Chiu Chuang >Assignee: Masatake Iwasaki > Fix For: 2.8.0 > > Attachments: HDFS-9358.001.patch, HDFS-9358.002.patch > > > I have seen this test failure occurred a few times in trunk: > Error Message > Timeout: excess replica count not equal to 2 for block blk_1073741825_1001 > after 2 msec. Last counts: live = 2, excess = 0, corrupt = 0 > Stacktrace > java.util.concurrent.TimeoutException: Timeout: excess replica count not > equal to 2 for block blk_1073741825_1001 after 2 msec. Last counts: live > = 2, excess = 0, corrupt = 0 > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:152) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:146) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.__CLR4_0_39bdgm666uf(TestNodeCount.java:130) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.testNodeCount(TestNodeCount.java:54) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-9358) TestNodeCount#testNodeCount timed out
[ https://issues.apache.org/jira/browse/HDFS-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15007951#comment-15007951 ] Hudson commented on HDFS-9358: -- FAILURE: Integrated in Hadoop-trunk-Commit #8810 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/8810/]) HDFS-9358. TestNodeCount#testNodeCount timed out. Contributed by (waltersu4549: rev 621cbb4f69072bde259f213629f84494416ae12f) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/blockmanagement/TestNodeCount.java > TestNodeCount#testNodeCount timed out > - > > Key: HDFS-9358 > URL: https://issues.apache.org/jira/browse/HDFS-9358 > Project: Hadoop HDFS > Issue Type: Bug > Components: test >Reporter: Wei-Chiu Chuang >Assignee: Masatake Iwasaki > Fix For: 2.8.0 > > Attachments: HDFS-9358.001.patch, HDFS-9358.002.patch > > > I have seen this test failure occurred a few times in trunk: > Error Message > Timeout: excess replica count not equal to 2 for block blk_1073741825_1001 > after 2 msec. Last counts: live = 2, excess = 0, corrupt = 0 > Stacktrace > java.util.concurrent.TimeoutException: Timeout: excess replica count not > equal to 2 for block blk_1073741825_1001 after 2 msec. Last counts: live > = 2, excess = 0, corrupt = 0 > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:152) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:146) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.__CLR4_0_39bdgm666uf(TestNodeCount.java:130) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.testNodeCount(TestNodeCount.java:54) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-9358) TestNodeCount#testNodeCount timed out
[ https://issues.apache.org/jira/browse/HDFS-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15007892#comment-15007892 ] Walter Su commented on HDFS-9358: - bq. It did not fail in 100 runs. Great. Thanks [~iwasakims]. +1 for last patch. > TestNodeCount#testNodeCount timed out > - > > Key: HDFS-9358 > URL: https://issues.apache.org/jira/browse/HDFS-9358 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Wei-Chiu Chuang >Assignee: Masatake Iwasaki > Attachments: HDFS-9358.001.patch, HDFS-9358.002.patch > > > I have seen this test failure occurred a few times in trunk: > Error Message > Timeout: excess replica count not equal to 2 for block blk_1073741825_1001 > after 2 msec. Last counts: live = 2, excess = 0, corrupt = 0 > Stacktrace > java.util.concurrent.TimeoutException: Timeout: excess replica count not > equal to 2 for block blk_1073741825_1001 after 2 msec. Last counts: live > = 2, excess = 0, corrupt = 0 > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:152) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:146) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.__CLR4_0_39bdgm666uf(TestNodeCount.java:130) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.testNodeCount(TestNodeCount.java:54) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-9358) TestNodeCount#testNodeCount timed out
[ https://issues.apache.org/jira/browse/HDFS-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15008065#comment-15008065 ] Hudson commented on HDFS-9358: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2613 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2613/]) HDFS-9358. TestNodeCount#testNodeCount timed out. Contributed by (waltersu4549: rev 621cbb4f69072bde259f213629f84494416ae12f) * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/blockmanagement/TestNodeCount.java > TestNodeCount#testNodeCount timed out > - > > Key: HDFS-9358 > URL: https://issues.apache.org/jira/browse/HDFS-9358 > Project: Hadoop HDFS > Issue Type: Bug > Components: test >Reporter: Wei-Chiu Chuang >Assignee: Masatake Iwasaki > Fix For: 2.8.0 > > Attachments: HDFS-9358.001.patch, HDFS-9358.002.patch > > > I have seen this test failure occurred a few times in trunk: > Error Message > Timeout: excess replica count not equal to 2 for block blk_1073741825_1001 > after 2 msec. Last counts: live = 2, excess = 0, corrupt = 0 > Stacktrace > java.util.concurrent.TimeoutException: Timeout: excess replica count not > equal to 2 for block blk_1073741825_1001 after 2 msec. Last counts: live > = 2, excess = 0, corrupt = 0 > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:152) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:146) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.__CLR4_0_39bdgm666uf(TestNodeCount.java:130) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.testNodeCount(TestNodeCount.java:54) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-9358) TestNodeCount#testNodeCount timed out
[
https://issues.apache.org/jira/browse/HDFS-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15006392#comment-15006392
]
Walter Su commented on HDFS-9358:
-
1. We can set heartBeat interval to 1s to shorten running time.
2. I think the 001 can patch solve the posted issue. Firstly thanks for that.
However I think the race condition still exists?
{code}
125 cluster.restartDataNode(dnprop);
126 cluster.waitActive();
127
128 // check if excessive replica is detected (transient)
129 initializeTimeout(TIMEOUT);
130 while (countNodes(block.getLocalBlock(), namesystem).excessReplicas()
!= 2) {
131 checkTimeout("excess replica count not equal to 2");
132 }
{code}
The old code expects 2 excessReplicas. The 001 patch expects 1 excessReplicas.
No matter how many excessReplicas we want, as you can see from the comment, the
state is "transient". What if the state vanished before line 130? It's unlikely
I know but the jenkins machine is under heavy load, who knows?
So I think we can disable block invalidation by setting large delay to make it
non-transient, then the test is more stable. Check
{{InvalidateBlocks.getInvalidationDelay()}}. Then we solved the issue and the
test logic changes in 001 patch is not required. How do you think?
> TestNodeCount#testNodeCount timed out
> -
>
> Key: HDFS-9358
> URL: https://issues.apache.org/jira/browse/HDFS-9358
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Wei-Chiu Chuang
>Assignee: Masatake Iwasaki
> Attachments: HDFS-9358.001.patch
>
>
> I have seen this test failure occurred a few times in trunk:
> Error Message
> Timeout: excess replica count not equal to 2 for block blk_1073741825_1001
> after 2 msec. Last counts: live = 2, excess = 0, corrupt = 0
> Stacktrace
> java.util.concurrent.TimeoutException: Timeout: excess replica count not
> equal to 2 for block blk_1073741825_1001 after 2 msec. Last counts: live
> = 2, excess = 0, corrupt = 0
> at
> org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:152)
> at
> org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:146)
> at
> org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.__CLR4_0_39bdgm666uf(TestNodeCount.java:130)
> at
> org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.testNodeCount(TestNodeCount.java:54)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HDFS-9358) TestNodeCount#testNodeCount timed out
[ https://issues.apache.org/jira/browse/HDFS-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15003753#comment-15003753 ] Masatake Iwasaki commented on HDFS-9358: Thanks for the confirmation, [~jojochuang]! > TestNodeCount#testNodeCount timed out > - > > Key: HDFS-9358 > URL: https://issues.apache.org/jira/browse/HDFS-9358 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Wei-Chiu Chuang >Assignee: Masatake Iwasaki > Attachments: HDFS-9358.001.patch > > > I have seen this test failure occurred a few times in trunk: > Error Message > Timeout: excess replica count not equal to 2 for block blk_1073741825_1001 > after 2 msec. Last counts: live = 2, excess = 0, corrupt = 0 > Stacktrace > java.util.concurrent.TimeoutException: Timeout: excess replica count not > equal to 2 for block blk_1073741825_1001 after 2 msec. Last counts: live > = 2, excess = 0, corrupt = 0 > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:152) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:146) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.__CLR4_0_39bdgm666uf(TestNodeCount.java:130) > at > org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.testNodeCount(TestNodeCount.java:54) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-9358) TestNodeCount#testNodeCount timed out
[
https://issues.apache.org/jira/browse/HDFS-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15002872#comment-15002872
]
Wei-Chiu Chuang commented on HDFS-9358:
---
[~iwasakims] Thanks for the patch.
I looked at the patch, and what it does is follows:
After NN detects DN is down, wait until the excess replica is invalidated,
before restarting the stopped DN again.
After the DN is restarted, make sure the excessive replica is detected.
So the process is deterministic and will always go like (granted no timeout)
{noformat}
(live, excess): (3, 1) -> (3, 0) -> (2, 1)
{noformat}
I don't have the committership, but looks good to me. I ran the patched test
and it did not fail in 100 runs.
> TestNodeCount#testNodeCount timed out
> -
>
> Key: HDFS-9358
> URL: https://issues.apache.org/jira/browse/HDFS-9358
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Wei-Chiu Chuang
>Assignee: Masatake Iwasaki
> Attachments: HDFS-9358.001.patch
>
>
> I have seen this test failure occurred a few times in trunk:
> Error Message
> Timeout: excess replica count not equal to 2 for block blk_1073741825_1001
> after 2 msec. Last counts: live = 2, excess = 0, corrupt = 0
> Stacktrace
> java.util.concurrent.TimeoutException: Timeout: excess replica count not
> equal to 2 for block blk_1073741825_1001 after 2 msec. Last counts: live
> = 2, excess = 0, corrupt = 0
> at
> org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:152)
> at
> org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.checkTimeout(TestNodeCount.java:146)
> at
> org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.__CLR4_0_39bdgm666uf(TestNodeCount.java:130)
> at
> org.apache.hadoop.hdfs.server.blockmanagement.TestNodeCount.testNodeCount(TestNodeCount.java:54)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HDFS-9358) TestNodeCount#testNodeCount timed out
[
https://issues.apache.org/jira/browse/HDFS-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15002355#comment-15002355
]
Hadoop QA commented on HDFS-9358:
-
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 11s
{color} | {color:blue} docker + precommit patch detected. {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} 3m
34s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 49s
{color} | {color:green} trunk passed with JDK v1.8.0_66 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 40s
{color} | {color:green} trunk passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
19s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 57s
{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
19s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
20s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 22s
{color} | {color:green} trunk passed with JDK v1.8.0_66 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 13s
{color} | {color:green} trunk passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
46s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 40s
{color} | {color:green} the patch passed with JDK v1.8.0_66 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 40s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 37s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 37s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
18s {color} | {color:green} the patch passed {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
16s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
22s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 23s
{color} | {color:green} the patch passed with JDK v1.8.0_66 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 9s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 88m 24s {color}
| {color:red} hadoop-hdfs in the patch failed with JDK v1.8.0_66. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 75m 36s {color}
| {color:red} hadoop-hdfs in the patch failed with JDK v1.7.0_79. {color} |
| {color:red}-1{color} | {color:red} asflicense {color} | {color:red} 0m 26s
{color} | {color:red} Patch generated 56 ASF License warnings. {color} |
| {color:black}{color} | {color:black} {color} | {color:black} 189m 55s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| JDK v1.8.0_66 Failed junit tests |
hadoop.hdfs.server.datanode.TestBlockScanner |
| | hadoop.hdfs.server.namenode.ha.TestEditLogTailer |
| | hadoop.hdfs.shortcircuit.TestShortCircuitCache |
| | hadoop.hdfs.server.datanode.TestDataNodeMetrics |
| | hadoop.hdfs.server.datanode.TestDataNodeVolumeFailure |
| | hadoop.hdfs.server.datanode.TestBlockReplacement |
| | hadoop.hdfs.server.namenode.ha.TestSeveralNameNodes |
| | hadoop.fs.viewfs.TestViewFileSystemAtHdfsRoot |
| | hadoop.fs.TestSymlinkHdfsFileContext |
| | hadoop.hdfs.TestAclsEndToEnd |
| | hadoop.hdfs.server.datanode.fsdataset.impl.TestLazyPersistReplicaRecovery
|
| |
