YARN-5544. TestNodeBlacklistingOnAMFailures fails on trunk. Contributed by Sunil G.

(cherry picked from commit 0d5997d2b9)
This commit is contained in:
Rohith Sharma K S 2016-08-23 10:33:28 +05:30
parent 854af9cee1
commit 71a3b01d51
1 changed files with 16 additions and 0 deletions

View File

@ -67,6 +67,9 @@ public class TestNodeBlacklistingOnAMFailures {
MockRM rm = startRM(conf, dispatcher);
CapacityScheduler scheduler = (CapacityScheduler) rm.getResourceScheduler();
// Register 5 nodes, so that we can blacklist atleast one if AM container
// is failed. As per calculation it will be like, 5nodes * 0.2 (default)=1.
// First register 2 nodes, and after AM lauched register 3 more nodes.
MockNM nm1 =
new MockNM("127.0.0.1:1234", 8000, rm.getResourceTrackerService());
nm1.registerNode();
@ -92,6 +95,19 @@ public class TestNodeBlacklistingOnAMFailures {
otherNode = nm1;
}
// register 3 nodes now
MockNM nm3 =
new MockNM("127.0.0.3:2345", 8000, rm.getResourceTrackerService());
nm3.registerNode();
MockNM nm4 =
new MockNM("127.0.0.4:2345", 8000, rm.getResourceTrackerService());
nm4.registerNode();
MockNM nm5 =
new MockNM("127.0.0.5:2345", 8000, rm.getResourceTrackerService());
nm5.registerNode();
// Set the exist status to INVALID so that we can verify that the system
// automatically blacklisting the node
makeAMContainerExit(rm, amContainerId, currentNode,