-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HDFS-15716. WaitforReplication in TestUpgradeDomainBlockPlacementPolicy #2528
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
💔 -1 overall
This message was automatically generated. |
7efa58e to
147f2ca
Compare
|
💔 -1 overall
This message was automatically generated. |
Does this is done outside TestUpgradeDomainBlockPlacementPolicy? Your patch looks applicable to branch-2.10 too. Since branch-2.10 still support Java 7, cherry-picking would be easy by avoiding lambda here. I think the lambda does not improve readability here. @amahussein |
Good point. I will remove the lambda. |
147f2ca to
def653a
Compare
jbrennan333
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 this looks good to me.
|
💔 -1 overall
This message was automatically generated. |
…cy (#2528) Contributed by Ahmed Hussein
| BlockPlacementStatus status = cluster.getNamesystem().getBlockManager(). | ||
| getBlockPlacementPolicy().verifyBlockPlacement( | ||
| block.getLocations(), REPLICATION_FACTOR); | ||
| assertTrue(status.isPlacementPolicySatisfied()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not leave this static import?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry @goiri I did not know that static imports are preferred. I remembered it used to be not favorable because of code readability.
I will take a note of that for future changes.
|
The list of failed unit tests in the last few days is getting worse and worse. |
Thanks @goiri. Test Result (23 failures / -45)
org.apache.hadoop.hdfs.server.balancer.TestBalancer.testBalancerWithStripedFile
org.apache.hadoop.hdfs.server.balancer.TestBalancer.testBalancerWithIncludeListWithPorts
org.apache.hadoop.hdfs.server.balancer.TestBalancer.testBalancerWithSortTopNodes
org.apache.hadoop.hdfs.server.balancer.TestBalancer.testBalancerCliWithIncludeListWithPorts
org.apache.hadoop.hdfs.server.blockmanagement.TestUnderReplicatedBlocks.testSetRepIncWithUnderReplicatedBlocks
org.apache.hadoop.hdfs.server.namenode.TestFsck.testECFsck
org.apache.hadoop.yarn.server.nodemanager.TestNodeStatusUpdater.testNodeDecommision
org.apache.hadoop.yarn.server.router.webapp.TestRouterWebServicesREST.testUpdateAppStateXML
org.apache.hadoop.yarn.server.router.webapp.TestRouterWebServicesREST.testAppQueueXML
org.apache.hadoop.yarn.server.router.webapp.TestRouterWebServicesREST.testAppTimeoutsXML
org.apache.hadoop.yarn.server.router.webapp.TestRouterWebServicesREST.testGetContainersXML
org.apache.hadoop.yarn.server.router.webapp.TestRouterWebServicesREST.testUpdateAppPriorityXML
org.apache.hadoop.yarn.server.router.webapp.TestRouterWebServicesREST.testUpdateAppQueueXML
org.apache.hadoop.yarn.server.router.webapp.TestRouterWebServicesREST.testAppTimeoutXML
org.apache.hadoop.yarn.server.router.webapp.TestRouterWebServicesREST.testAppAttemptXML
org.apache.hadoop.yarn.server.router.webapp.TestRouterWebServicesREST.testGetAppAttemptXML
org.apache.hadoop.yarn.server.router.webapp.TestRouterWebServicesREST.testAppXML
org.apache.hadoop.yarn.server.router.webapp.TestRouterWebServicesREST.testAppStateXML
org.apache.hadoop.yarn.server.router.webapp.TestRouterWebServicesREST.testAppPriorityXML
org.apache.hadoop.yarn.server.router.webapp.TestRouterWebServicesREST.testGetAppsMultiThread
org.apache.hadoop.tools.dynamometer.TestDynamometerInfra.org.apache.hadoop.tools.dynamometer.TestDynamometerInfra
org.apache.hadoop.yarn.applications.distributedshell.TestDistributedShell.testDSShellWithOpportunisticContainers
org.apache.hadoop.yarn.applications.distributedshell.TestDistributedShell.testDSShellWithEnforceExecutionType
By the way, I found that TestDistributedShell does not clean at all. The problem that the two failing unit tests leave several processes running for sometime. It could be one of the reasons the system crashes as the background containers are sucking memory and CPU resources. |
In some slow runs
TestUpgradeDomainBlockPlacementPolicy#testPlacementandTestUpgradeDomainBlockPlacementPolicy#testPlacementAfterDecommissionfail.On branch-2.10, this was fixed by waiting for the replication to be complete.