[ 
https://issues.apache.org/jira/browse/YARN-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14737599#comment-14737599
 ] 

Wangda Tan commented on YARN-4114:
----------------------------------

[~bibinchundatt], thanks for reporting this, I think we'd better not change 
this:
- It's not intrusive in xml, but actually, it's standard way to express an 
array in xml. When you viewing json version of the scheduler REST API, you can 
found:
{code}
            "nodeLabels": [
              "x",
              "y"
            ],
{code}

- It is released in 2.7 already, we need make API compatible.

Let me know your thoughts. And please close this ticket if you agree with me.

Thanks,



> In RM  REST API for cluster/scheduler accessibleLabels in queues not listed 
> properly
> ------------------------------------------------------------------------------------
>
>                 Key: YARN-4114
>                 URL: https://issues.apache.org/jira/browse/YARN-4114
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>            Reporter: Bibin A Chundatt
>            Assignee: Bibin A Chundatt
>         Attachments: 0001-YARN-4114.patch, 0002-YARN-4114.patch
>
>
> *Request used*
> Accept: application/xml
> GET http://<rm http address:port>/ws/v1/cluster/scheduler
> Response
> {code}
> <queue xsi:type="capacitySchedulerLeafQueueInfo">
> <capacity>10.0</capacity>
> ...
> <state>RUNNING</state>
> <resourcesUsed>...</resourcesUsed>
> <hideReservationQueues>false</hideReservationQueues>
> <nodeLabels>1</nodeLabels>
> <nodeLabels>3</nodeLabels>
> <allocatedContainers>0</allocatedContainers>
> <reservedContainers>0</reservedContainers>
> <pendingContainers>0</pendingContainers>
> ..
> </queue>
> {code}
> Nodelabels for queue should be as below
> <nodeLabels>
>    <nodeLabel>1</nodeLabel>
>    <nodeLabel>3</nodeLabel>
> </nodeLabels>
> or 
> <nodeLabels>1,3</nodeLabels>



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

Reply via email to