Apache/hadoop
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

YARN-6480. Timeout is too aggressive for TestAMRestart.testPreemptedAMRestartOnRMRestart. Contributed by Eric Badger

Browse Source 
(cherry picked from commit 416880550214e58f2284a045ad0c96ba4aa78ea8)
This commit is contained in:
Jason Lowe 2017-04-14 17:15:48 -05:00
parent 53da65ef8b
commit 1699b20526
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/applicationsmanager/TestAMRestart.java
View File

@ -490,7 +490,7 @@ public void testShouldNotCountFailureToMaxAttemptRetry() throws Exception {
// Test RM restarts after AM container is preempted, new RM should not count // Test RM restarts after AM container is preempted, new RM should not count
// AM preemption failure towards the max-retry-account and should be able to // AM preemption failure towards the max-retry-account and should be able to
// re-launch the AM. // re-launch the AM.
@Test(timeout = 20000) @Test(timeout = 60000)
public void testPreemptedAMRestartOnRMRestart() throws Exception { public void testPreemptedAMRestartOnRMRestart() throws Exception {
YarnConfiguration conf = new YarnConfiguration(); YarnConfiguration conf = new YarnConfiguration();
conf.setClass(YarnConfiguration.RM_SCHEDULER, CapacityScheduler.class, conf.setClass(YarnConfiguration.RM_SCHEDULER, CapacityScheduler.class,