hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohith Sharma K S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4614) TestApplicationPriority#testApplicationPriorityAllocationWithChangeInPriority fails occasionally
Date Sat, 23 Jan 2016 02:20:39 GMT

    [ https://issues.apache.org/jira/browse/YARN-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15113479#comment-15113479
] 

Rohith Sharma K S commented on YARN-4614:
-----------------------------------------

thanks [~sunilg] for your analysis. It make sense to me. I verified the test using debug point
in eclipse, as you said that one extra node heartbeat kick off scheduling and allocate a container
which attempt goes to ALLOCATED state. And also I verified test with patch using debug mode,
test cases passes.

> TestApplicationPriority#testApplicationPriorityAllocationWithChangeInPriority fails occasionally
> ------------------------------------------------------------------------------------------------
>
>                 Key: YARN-4614
>                 URL: https://issues.apache.org/jira/browse/YARN-4614
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: test
>         Environment: jenkins
>            Reporter: Jason Lowe
>            Assignee: Sunil G
>         Attachments: 0001-YARN-4614.patch
>
>
> TestApplicationPriority#testApplicationPriorityAllocationWithChangeInPriority has sporadically
failed in precommit builds.  Sample failure:
> {noformat}
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support
was removed in 8.0
> Running org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestApplicationPriority
> Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 116.776 sec <<<
FAILURE! - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestApplicationPriority
> testApplicationPriorityAllocationWithChangeInPriority(org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestApplicationPriority)
 Time elapsed: 50.687 sec  <<< FAILURE!
> java.lang.AssertionError: Attempt state is not correct (timedout): expected: SCHEDULED
actual: ALLOCATED for the application attempt appattempt_1453255879005_0002_000001
> 	at org.junit.Assert.fail(Assert.java:88)
> 	at org.apache.hadoop.yarn.server.resourcemanager.MockRM.waitForState(MockRM.java:197)
> 	at org.apache.hadoop.yarn.server.resourcemanager.MockRM.waitForState(MockRM.java:172)
> 	at org.apache.hadoop.yarn.server.resourcemanager.MockRM.waitForAttemptScheduled(MockRM.java:831)
> 	at org.apache.hadoop.yarn.server.resourcemanager.MockRM.launchAM(MockRM.java:818)
> 	at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestApplicationPriority.testApplicationPriorityAllocationWithChangeInPriority(TestApplicationPriority.java:494)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message