[
https://issues.apache.org/jira/browse/YARN-10084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17020605#comment-17020605
]
Eric Payne commented on YARN-10084:
-----------------------------------
{quote}
For some reason, I was under the impression that < 0 meant unlimited, but the
documentation clearly says " Any value less than or equal to zero will be
considered as disabled."
{quote}
Sorry, spoke too soon. As you pointed out in your second comment, this specific
code was unchanged, it was just moved from LeafQueue to AbstractCSQueue. Also,
it should be checking for > 0 and not >= 0, because <= 0 means no max lifetime.
bq. Should we be inheriting the parent queue's max if the leaf queue's max is
zero?
I think so. I'll think about this some more, but a child queue should not have
a max lifetime longer than its parent's max lifetime in my opinion.
> 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
