[
https://issues.apache.org/jira/browse/YARN-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
forrestchen updated YARN-4022:
------------------------------
Description:
When I delete an existing queue by modify the xxx-schedule.xml, I can still see
the queue information block in webpage(/cluster/scheduler) though the 'Min
Resources' items all become to zero and have no item of 'Max Running
Applications'.
I can still submit an application to the deleted queue and the application will
run using 'root.default' queue instead, but submit to an un-exist queue will
cause an exception.
My expectation is the deleted queue will not displayed in webpage and submit
application to the deleted queue will act just like the queue doesn't exist.
PS: There's no application running in the queue I delete.
Some related config in yarn-site.xml:
{code}
<property>
<name>yarn.scheduler.fair.user-as-default-queue</name>
<value>false</value>
</property>
<property>
<name>yarn.scheduler.fair.allow-undeclared-pools</name>
<value>false</value>
</property>
{code}
a related question is here:
http://stackoverflow.com/questions/26488564/hadoop-yarn-why-the-queue-cannot-be-deleted-after-i-revise-my-fair-scheduler-xm
was:
When I delete an existing queue by modify the xxx-schedule.xml, I can still see
the queue information block in webpage(/cluster/scheduler) though the 'Min
Resources' items all become to zero and have no item of 'Max Running
Applications'.
I can still submit an application to the deleted queue and the application will
run using 'root.default' queue instead, but submit to an un-exist queue will
cause an exception.
My expectation is the deleted queue will not displayed in webpage and submit
application to the deleted queue will act just like the queue doesn't exist.
PS: There's no application running in the queue I delete.
Some related config in yarn-site.xml:
{code}
<property>
<name>yarn.scheduler.fair.user-as-default-queue</name>
<value>false</value>
</property>
<property>
<name>yarn.scheduler.fair.allow-undeclared-pools</name>
<value>false</value>
</property>
{code}
> queue not remove from webpage(/cluster/scheduler) when delete queue in
> xxx-scheduler.xml
> ----------------------------------------------------------------------------------------
>
> Key: YARN-4022
> URL: https://issues.apache.org/jira/browse/YARN-4022
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Reporter: forrestchen
>
> When I delete an existing queue by modify the xxx-schedule.xml, I can still
> see the queue information block in webpage(/cluster/scheduler) though the
> 'Min Resources' items all become to zero and have no item of 'Max Running
> Applications'.
> I can still submit an application to the deleted queue and the application
> will run using 'root.default' queue instead, but submit to an un-exist queue
> will cause an exception.
> My expectation is the deleted queue will not displayed in webpage and submit
> application to the deleted queue will act just like the queue doesn't exist.
> PS: There's no application running in the queue I delete.
> Some related config in yarn-site.xml:
> {code}
> <property>
> <name>yarn.scheduler.fair.user-as-default-queue</name>
> <value>false</value>
> </property>
> <property>
> <name>yarn.scheduler.fair.allow-undeclared-pools</name>
> <value>false</value>
> </property>
> {code}
> a related question is here:
> http://stackoverflow.com/questions/26488564/hadoop-yarn-why-the-queue-cannot-be-deleted-after-i-revise-my-fair-scheduler-xm
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
