Richard Lee commented on YARN-4191:

AFAICT, looking at the yarn source code, the RM doesn't actually serialize the 
ApplicationReport. It gets a lot of similar information about the 
ApplicationMaster and returns it on the REST /apps endpoint. One thing that 
seems to be missing is the RPC port, tho.  In particular, I'm interested in 
working with the Samza Application Master. It has both a trackingUrl port and 
an RPC port.  The REST stuff is on the RPC port at / (with, oddly no version 
path or anything, which seems not the best practice).  Compare this to the Map 
Reduce ApplicationMaster, where the REST api is on the same port as the 
trackingUrl at /ws/v1/mapreduce. 

I was not aware of the other RM REST issues. However, at present, I've only 
been doing GET requests to retrieve information about the running cluster, and 
not yet trying to control it.

> Expose ApplicationMaster RPC port in ResourceManager REST endpoint
> ------------------------------------------------------------------
>                 Key: YARN-4191
>                 URL: https://issues.apache.org/jira/browse/YARN-4191
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>    Affects Versions: 2.7.1
>            Reporter: Richard Lee
>            Priority: Minor
> Currently, the ResourceManager REST endpoint returns only the trackingUrl for 
> the ApplicationMaster.  Some AMs, however, have their REST endpoints on the 
> RPC port.  However, the RM does not expose the AM RPC port via REST for some 
> reason.

This message was sent by Atlassian JIRA

Reply via email to