[SAMZA-777] Samza AM REST API not reachable from RM REST API, and not versioned

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 0.9.1
• Component/s: yarn
• Assignee: Unassigned
• Reporter: Richard Lee
• Created: 23/Sep/15 21:35
• Updated: 26/Sep/15 01:16

Description

The Samza AM REST api is only available on the RPC port. Yet, for 'reasons', the RM REST api does not expose the RPC port of the AM. One potential justification is that all request from clients to the AM via the RM should go through the RM proxy, as happens for the trackingUrl, which is obtainable via the RM REST API.

Note, however, that the MapReduce AM REST API is provided under the trackingUrl, so it is available via the RM REST API. Also, the MapReduce REST endpoint is at '/ws/v1/mapreduce', which allows them to a) version the API, and b) provide additional services on the same port.

I think that Samza's AM should follow the same pattern. The Samza AM REST API should be reachable under the same port as the trackingUrl at path '/ws/v1/samza'. The REST API could also still be made available at an unversioned path on the RPC port.

I have made such a change in my tree, and verified that it solves the issue.