[
https://issues.apache.org/jira/browse/YARN-10084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17020435#comment-17020435
]
Jim Brennan commented on YARN-10084:
------------------------------------
(responding to my own comment)
Actually, I think the question is really about getInheritedMaxAppLifetime().
(The other code is unchanged from before.) Should we be inheriting the parent
queue's max if the leaf queue's max is zero? Current patch keeps the leaf
queue max at zero in this case. Maybe this is correct, as the way to
explicitly set no max in a leaf where the parent has one?
> 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
>
>
> 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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
