[
https://issues.apache.org/jira/browse/YARN-10084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17023225#comment-17023225
]
Eric Payne commented on YARN-10084:
-----------------------------------
All patches are uploaded. Here is the breakdown of the differences:
- branch-3.2: Due to changes made to MockRM#submitApp in YARN-9052, and since
YARN-9052 was not backported, new unit tests in this JIRA had to use a
different submitApp method in branch-3.2
-branch-3.1: The most obvious choice for the correct submitApp method that was
used in branch-3.2 did not exist in branch-3.1.
- branch-2.10: In AbstractCSQueue#setupQueueConfigs was not passed the
CapacitySchedulerConfiguration as a method parameter in 2.10, so I had to get
it from the CS context.
> Allow inheritance of max app lifetime / default app lifetime
> ------------------------------------------------------------
>
> Key: YARN-10084
> URL: https://issues.apache.org/jira/browse/YARN-10084
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacity scheduler
> Affects Versions: 2.10.0, 3.2.1, 3.1.3
> Reporter: Eric Payne
> Assignee: Eric Payne
> Priority: Major
> Attachments: YARN-10084.001.patch, YARN-10084.002.patch,
> YARN-10084.003.patch, YARN-10084.004.patch, YARN-10084.005.patch,
> YARN-10084.branch-2.10.005.patch, YARN-10084.branch-3.1.005.patch,
> YARN-10084.branch-3.2.005.patch
>
>
> Currently, {{maximum-application-lifetime}} and
> {{default-application-lifetime}} must be set for each leaf queue. If it is
> not set for a particular leaf queue, then there will be no time limit on apps
> running in that queue. It should be possible to set
> {{yarn.scheduler.capacity.root.maximum-application-lifetime}} for the root
> queue and allow child queues to override that value if desired.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
