[
https://issues.apache.org/jira/browse/OOZIE-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13670054#comment-13670054
]
Rohini Palaniswamy commented on OOZIE-1395:
-------------------------------------------
+1
> Using Yarn's CapacityScheduler causes some tests to time out
> ------------------------------------------------------------
>
> Key: OOZIE-1395
> URL: https://issues.apache.org/jira/browse/OOZIE-1395
> Project: Oozie
> Issue Type: Bug
> Components: tests
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Fix For: trunk
>
> Attachments: OOZIE-1395.patch, OOZIE-1395.patch
>
>
> When using Yarn's CapacityScheduler, we've seen some tests time out (usually
> TestPigActionExecutor, but sometimes some other actions as well).
> The problem is that the AM doing the launcher AM is taking up enough
> resources that any launched job gets queued by YARN (to be run when the
> launcher finishes). Because the launcher job is waiting until the launched
> job(s) finish, we get a deadlock and the test eventually times out.
> We can fix this by increasing
> {{yarn.scheduler.capacity.maximum-am-resource-percent}} from the default of
> 0.1 to say 0.5 to allow more resources to be used by the AMs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
