[
https://issues.apache.org/jira/browse/TEZ-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Eagles updated TEZ-619:
--------------------------------
Attachment: TEZ-619.patch
After examining the log files in the failed case vs the success case, I saw the
the container was being allocated on host4 instead of host3. The caused me to
find the container priority was incorrectly configured for one of the
containers. The equal priorities of host3 and host4 caused the intermittent
errors in this test.
> Failing test: TestTaskScheduler.testTaskSchedulerWithReuse
> ----------------------------------------------------------
>
> Key: TEZ-619
> URL: https://issues.apache.org/jira/browse/TEZ-619
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Hitesh Shah
> Assignee: Jonathan Eagles
> Priority: Blocker
> Attachments: TEZ-619.patch
>
>
> TestTaskScheduler.testTaskSchedulerWithReuse:604
> Wanted but not invoked:
> taskSchedulerAppCallback.taskAllocated(
> Mock for ClassWithSuperclassToWorkAroundCglibBug, hashCode: 22358902,
> Mock for ClassWithSuperclassToWorkAroundCglibBug, hashCode: 26357574,
> Mock for Container, hashCode: 33000296
> );
> -> at
> org.apache.tez.dag.app.rm.TestTaskScheduler.testTaskSchedulerWithReuse(TestTaskScheduler.java:604)
> However, there were other interactions with this mock:
> -> at
> org.apache.tez.dag.app.rm.TaskSchedulerAppCallbackWrapper$SetApplicationRegistrationDataCallable.call(TaskSchedulerAppCallbackWrapper.java:252)
> -> at
> org.apache.tez.dag.app.rm.TaskSchedulerAppCallbackWrapper$TaskAllocatedCallable.call(TaskSchedulerAppCallbackWrapper.java:160)
> -> at
> org.apache.tez.dag.app.rm.TaskSchedulerAppCallbackWrapper$TaskAllocatedCallable.call(TaskSchedulerAppCallbackWrapper.java:160)
> -> at
> org.apache.tez.dag.app.rm.TaskSchedulerAppCallbackWrapper$TaskAllocatedCallable.call(TaskSchedulerAppCallbackWrapper.java:160)
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
