[
https://issues.apache.org/jira/browse/YARN-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15802255#comment-15802255
]
Wangda Tan commented on YARN-5556:
----------------------------------
Just offline discussed with [~xgong].
I think we don't need the additional DELETED state, first it generate some
maintenance overheads, for example we need to maintain state transition to/from
of the DELETED state. And since by design a queue can be deleted only if queue
is stopped and no app running, so the impact of typo should be minimum. Our
preference is simply remove queue from config.
And for re-distribution of stopped/deleted queue. For delete queue it should be
obvious, since the queue is gone, sum of its siblings should be 100. For
stopped queue, our expectation is, it will be reactivated at some time. So it
will be better to keep the capacity as-is, and admin can update max-capacity of
its siblings to make sure queue capacity can be utilized.
I think we need to update design doc to make it up-to-date.
Thoughts?
> Support for deleting queues without requiring a RM restart
> ----------------------------------------------------------
>
> Key: YARN-5556
> URL: https://issues.apache.org/jira/browse/YARN-5556
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn
> Reporter: Xuan Gong
> Assignee: Naganarasimha G R
> Attachments: YARN-5556.v1.001.patch, YARN-5556.v1.002.patch,
> YARN-5556.v1.003.patch, YARN-5556.v1.004.patch
>
>
> Today, we could add or modify queues without restarting the RM, via a CS
> refresh. But for deleting queue, we have to restart the ResourceManager. We
> could support for deleting queues without requiring a RM restart
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
