[jira] [Updated] (YARN-11971) Capacity Scheduler UI - label assign to queue does not disappear to after deleting it

["chhinlinghean (Jira)" <ji...@apache.org>]

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

chhinlinghean updated YARN-11971:
---------------------------------
    Description: 
*Steps to reproduce:*
 # Create root.\{queue_name}

 # Create a node label with assign hosts

 # Assign the created label to that queue only

 # Assign capacity in the label partition view to both the new create queue and the root.default

 # Delete the created queue and the label

 # Try to create queue under root.default

 # It will throw validation error 400 bad request

 
RM logs shows that the label is assigned to root.default queue despite deleting the label and only assign the label to the new created queue.
 
 
|WARN|RMWebServices|CapacityScheduler configuration validation failed:java.io.IOException: Failed to re-init queues : Illegal capacity sum of 0.0 for children of queue default for label=label3. It is set to 0, but parent percent != 0, and doesn't
allow children capacity to set to 0|

The problem is that queue capacity could be set in partition view even though the queue does not have access to that label. Leaving the only queue's label capacity in /scheduler-conf endpoint. E.g. 

<property>

<name>yarn.scheduler.capacity.root.default.accessible-node-labels.label3.capacity</name>

<value>100</value>

</property>
```
A new validation is needed to make sure the queue has access to the label before allowing to set capacity in the partition view.

  was:
*Steps to reproduce:*
 # Create root.\{queue_name}

 # Create a node label with assign hosts

 # Assign the created label to that queue only

 # Assign capacity in the label partition view to both the new create queue and the root.default

 # Delete the created queue and the label

 # Try to create queue under root.default

 # It will throw validation error 400 bad request

 
RM logs shows that the label is assigned to root.default queue despite deleting the label and only assign the label to the new created queue.
 
 
|WARN|RMWebServices|CapacityScheduler configuration validation failed:java.io.IOException: Failed to re-init queues : Illegal capacity sum of 0.0 for children of queue default for label=label3. It is set to 0, but parent percent != 0, and doesn't
allow children capacity to set to 0|


The problem is that queue capacity could be set in partition view even though the queue does not have access to that label. Leaving the only queue's label capacity in /scheduler-conf endpoint. E.g. 
```

<property>

<name>yarn.scheduler.capacity.root.default.accessible-node-labels.label3.capacity</name>

<value>100</value>

</property>
```
A new validation is needed to make sure the queue has access to the label before allowing to set capacity in the partition view.


> Capacity Scheduler UI - label assign to queue does not disappear to after deleting it
> -------------------------------------------------------------------------------------
>
>                 Key: YARN-11971
>                 URL: https://issues.apache.org/jira/browse/YARN-11971
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn
>    Affects Versions: 3.5.0
>            Reporter: chhinlinghean
>            Assignee: chhinlinghean
>            Priority: Major
>
> *Steps to reproduce:*
>  # Create root.\{queue_name}
>  # Create a node label with assign hosts
>  # Assign the created label to that queue only
>  # Assign capacity in the label partition view to both the new create queue and the root.default
>  # Delete the created queue and the label
>  # Try to create queue under root.default
>  # It will throw validation error 400 bad request
>  
> RM logs shows that the label is assigned to root.default queue despite deleting the label and only assign the label to the new created queue.
>  
>  
> |WARN|RMWebServices|CapacityScheduler configuration validation failed:java.io.IOException: Failed to re-init queues : Illegal capacity sum of 0.0 for children of queue default for label=label3. It is set to 0, but parent percent != 0, and doesn't
> allow children capacity to set to 0|
> The problem is that queue capacity could be set in partition view even though the queue does not have access to that label. Leaving the only queue's label capacity in /scheduler-conf endpoint. E.g. 
> <property>
> <name>yarn.scheduler.capacity.root.default.accessible-node-labels.label3.capacity</name>
> <value>100</value>
> </property>
> ```
> A new validation is needed to make sure the queue has access to the label before allowing to set capacity in the partition view.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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