You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Xuan Gong (JIRA)" <ji...@apache.org> on 2016/10/19 21:13:58 UTC

[jira] [Updated] (YARN-5724) [Umbrella] Better Queue Management in YARN

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

Xuan Gong updated YARN-5724:
----------------------------
    Attachment: Designdocv1-Configuration-basedQueueManagementinYARN.pdf

> [Umbrella] Better Queue Management in YARN
> ------------------------------------------
>
>                 Key: YARN-5724
>                 URL: https://issues.apache.org/jira/browse/YARN-5724
>             Project: Hadoop YARN
>          Issue Type: Task
>            Reporter: Xuan Gong
>            Assignee: Xuan Gong
>         Attachments: Designdocv1-Configuration-basedQueueManagementinYARN.pdf
>
>
> This serves as an umbrella ticket for tasks related to better queue management in YARN.
> Today's the only way to manage the queue is through admins editing configuration files and then issuing a refresh command. This will bring many inconveniences. For example, the users can not create / delete /modify their own queues without talking to site level admins.
> Even in today's approach (configuration-based), we still have several places needed to improve: 
> *  It is possible today to add or modify queues without restarting the RM, via a CS refresh. But for deleting queue, we have to restart the resourcemanager.
> * When a queue is STOPPED, resources allocated to the queue can be handled better. Currently, they'll only be used if the other queues are setup to go over their capacity.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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