hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohith Sharma K S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6600) Enhance default lifetime of application at LeafQueue level.
Date Tue, 05 Sep 2017 09:09:01 GMT

    [ https://issues.apache.org/jira/browse/YARN-6600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153330#comment-16153330

Rohith Sharma K S commented on YARN-6600:

Here are offline discussion summary on above comments
bq. But could be configured as 0 also, is that invalid ?
Yes, 0 and -1 are invalid. It is documented in both capacity-scheduler.xml and capacityscheduler.md

bq. Is it possible that admin might not know how much max some special app may run?
It is pretty debatable topic. As we discussed, if admin required to do so, he can directly
configure max lifetime and disable default lifetime. I will update patch to handle this case
so that max lifetime is considered as default lifetime if admin misses to configure.

bq. we could return with maximumApplicationLifetime
make sense to me

bq. If maximumApplicationLifetime is not configured, we ll get Long.MAX_VALUE for queueMaxLifetimeInSec.
Good catch! Its a major comment :P As discussed offline, lets introduce new scheduler API
getMaximumApplicationLifetime(String queueName), During update, default lifetime does not
take any precedency!!

5th, 6th, and 7th comments make sense me and I will update those in next patch.

> Enhance default lifetime of application at LeafQueue level.
> -----------------------------------------------------------
>                 Key: YARN-6600
>                 URL: https://issues.apache.org/jira/browse/YARN-6600
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacity scheduler
>            Reporter: Rohith Sharma K S
>            Assignee: Rohith Sharma K S
>         Attachments: YARN-6600.01.patch, YARN-6600.02.patch, [YARN-6600] Extend lifetime
to scheduler Leaf Queue.pdf
> Setting timeout at LeafQueue level allows admin to control from bad apps which uses most
of the resources for all the time. 
> Example : Any application submitted to particular queue i.e QUEUE-1 should not  run more
than N hours. Even user set lifetime as N+1 hour, the application will be killed after N hours.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message