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

Weiwei Yang commented on YARN-8559:
-----------------------------------

Hi [~suma.shivaprasad]/[~leftnoteasy]

Thanks for the comments.

bq. Can you pls add documentation in ResourceManagerRest.md

Sure, will update in next patch.

bq. can we use the existing logic similar to ConfServlet?

I think we should stick to the JAX-RS pattern in RMWebService, that is more 
consistent. Also it is easier to support both standard json/xml content type 
without parsing the request. After all DAO is just a wrapper, non-functional 
change.

bq. it might be better to protect access of the REST endpoint by admin

Make sense to me, will update in next patch.

Thanks

> Expose mutable-conf scheduler's configuration in RM /scheduler-conf endpoint
> ----------------------------------------------------------------------------
>
>                 Key: YARN-8559
>                 URL: https://issues.apache.org/jira/browse/YARN-8559
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>            Reporter: Anna Savarin
>            Assignee: Weiwei Yang
>            Priority: Major
>         Attachments: YARN-8559.001.patch, YARN-8559.002.patch, 
> YARN-8559.003.patch
>
>
> All Hadoop services provide a set of common endpoints (/stacks, /logLevel, 
> /metrics, /jmx, /conf).  In the case of the Resource Manager, part of the 
> configuration comes from the scheduler being used.  Currently, these 
> configuration key/values are not exposed through the /conf endpoint, thereby 
> revealing an incomplete configuration picture. 
> Make an improvement and expose the scheduling configuration info through the 
> RM's /conf endpoint.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to