[ 
https://issues.apache.org/jira/browse/YARN-8564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

zhuqi updated YARN-8564:
------------------------
    Description: I wish to have application lifetime monitor for queue level in 
FairSheduler. In our large yarn cluster, sometimes there are too many small 
jobs in one minor queue but may run too long, it may affect our our high 
priority and very important queue . If we can have queue level application 
lifetime monitor in the queue level, and set small lifetime in the minor queue. 
 (was: I wish to have application lifetime monitor for queue level in 
FairSheduler. In our large yarn cluster, sometimes there are too many small 
jobs in one minor queue but may run too long, it may cause our long time job in 
our high priority and very important queue pending too many times. If we can 
have queue level application lifetime monitor in the queue level, and set small 
lifetime in the minor queue, i think it may can solve our problems before the 
global schedulering can be used in FairScheduler.)

> Add queue level application lifetime monitor in FairScheduler 
> --------------------------------------------------------------
>
>                 Key: YARN-8564
>                 URL: https://issues.apache.org/jira/browse/YARN-8564
>             Project: Hadoop YARN
>          Issue Type: Wish
>          Components: fairscheduler
>    Affects Versions: 3.1.0
>            Reporter: zhuqi
>            Priority: Major
>
> I wish to have application lifetime monitor for queue level in FairSheduler. 
> In our large yarn cluster, sometimes there are too many small jobs in one 
> minor queue but may run too long, it may affect our our high priority and 
> very important queue . If we can have queue level application lifetime 
> monitor in the queue level, and set small lifetime in the minor queue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to