[
https://issues.apache.org/jira/browse/YARN-10084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17021287#comment-17021287
]
Eric Payne commented on YARN-10084:
-----------------------------------
Okay. Thanks for your further analysis, [~Jim_Brennan].
bq. a child queue should not have a max lifetime longer than its parent's max
lifetime
After thinking about it more, there is no reason a child queue can't have a
larger max lifetime than a parent queue.
{quote}
What if you want only one queue to have no max? How would you configure that?
Would be nice if you could specify the max at the root once, and only specify
zero on the long job queue to specify that it has no max.
{quote}
So, >= 0 means that the max lifetime was set in the config and it should be
used. < 0 means use the parent's max lifetime value. If root queue, then < 0
means no lifetime value, and that will be inherited by child queues unless
overridden.
> 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
>
>
> 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]
