[
https://issues.apache.org/jira/browse/YARN-6600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065656#comment-16065656
]
Rohith Sharma K S commented on YARN-6600:
-----------------------------------------
High level changes on the patch
# introduced CS scheduler config key to load max lifetime value.
# On submission, RMAppImpl validate for scheduler max lifetime value and sets
accordingly.
# On update, RMAppManager validate for scheduler max lifetime value. If updated
value exceeds queue max lifetime value than cut off to scheduler max queue
lifetime and send new timeout value in response.
# Changed update response proto that carries new timeout value in iso8601
format.
# tests are modified accordingly
> 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] 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
