[ https://issues.apache.org/jira/browse/HDFS-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572969#comment-16572969 ]
Brahma Reddy Battula commented on HDFS-7524: -------------------------------------------- [~RANith] thanks for uploading the patch. AFAIK, this is broken by HDFS-12840 as it's changed the DataNode number from 3 to 10. So it's taking some more time to clear the invalid replica. Approach looks good but we might need to wait till it clear..Looks we can't change back the DN number to 3 as EC testcases might fail. if there are no objections we can gohead with commit,will hold till this week. > TestRetryCacheWithHA.testUpdatePipeline fails occasionally in trunk > ------------------------------------------------------------------- > > Key: HDFS-7524 > URL: https://issues.apache.org/jira/browse/HDFS-7524 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode, test > Reporter: Yongjun Zhang > Assignee: Ranith Sardar > Priority: Major > Labels: flaky-test > Attachments: HDFS-7524-001.patch > > > https://builds.apache.org/job/Hadoop-Hdfs-trunk/1974/testReport/ > Error Message > {quote} > After waiting the operation updatePipeline still has not taken effect on NN > yet > Stacktrace > java.lang.AssertionError: After waiting the operation updatePipeline still > has not taken effect on NN yet > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at > org.apache.hadoop.hdfs.server.namenode.ha.TestRetryCacheWithHA.testClientRetryWithFailover(TestRetryCacheWithHA.java:1278) > at > org.apache.hadoop.hdfs.server.namenode.ha.TestRetryCacheWithHA.testUpdatePipeline(TestRetryCacheWithHA.java:1176) > {quote} > Found by tool proposed in HADOOP-11045: > {quote} > [yzhang@localhost jenkinsftf]$ ./determine-flaky-tests-hadoop.py -j > Hadoop-Hdfs-trunk -n 5 | tee bt.log > ****Recently FAILED builds in url: > https://builds.apache.org//job/Hadoop-Hdfs-trunk > THERE ARE 4 builds (out of 6) that have failed tests in the past 5 days, > as listed below: > ===>https://builds.apache.org/job/Hadoop-Hdfs-trunk/1974/testReport > (2014-12-15 03:30:01) > Failed test: > org.apache.hadoop.hdfs.TestDecommission.testIncludeByRegistrationName > Failed test: > org.apache.hadoop.hdfs.server.blockmanagement.TestDatanodeManager.testNumVersionsReportedCorrect > Failed test: > org.apache.hadoop.hdfs.server.namenode.ha.TestRetryCacheWithHA.testUpdatePipeline > ===>https://builds.apache.org/job/Hadoop-Hdfs-trunk/1972/testReport > (2014-12-13 10:32:27) > Failed test: > org.apache.hadoop.hdfs.TestDecommission.testIncludeByRegistrationName > ===>https://builds.apache.org/job/Hadoop-Hdfs-trunk/1971/testReport > (2014-12-13 03:30:01) > Failed test: > org.apache.hadoop.hdfs.server.namenode.ha.TestRetryCacheWithHA.testUpdatePipeline > ===>https://builds.apache.org/job/Hadoop-Hdfs-trunk/1969/testReport > (2014-12-11 03:30:01) > Failed test: > org.apache.hadoop.hdfs.server.blockmanagement.TestDatanodeManager.testNumVersionsReportedCorrect > Failed test: > org.apache.hadoop.hdfs.server.namenode.ha.TestRetryCacheWithHA.testUpdatePipeline > Failed test: > org.apache.hadoop.hdfs.server.namenode.ha.TestPipelinesFailover.testFailoverRightBeforeCommitSynchronization > Among 6 runs examined, all failed tests <#failedRuns: testName>: > 3: > org.apache.hadoop.hdfs.server.namenode.ha.TestRetryCacheWithHA.testUpdatePipeline > 2: org.apache.hadoop.hdfs.TestDecommission.testIncludeByRegistrationName > 2: > org.apache.hadoop.hdfs.server.blockmanagement.TestDatanodeManager.testNumVersionsReportedCorrect > 1: > org.apache.hadoop.hdfs.server.namenode.ha.TestPipelinesFailover.testFailoverRightBeforeCommitSynchronization > {quote} -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org