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

["Richard Lee (JIRA)" <ji...@apache.org>]

Richard Lee created SAMZA-777:
---------------------------------

             Summary: Samza AM REST API not reachable from RM REST API, and not versioned
                 Key: SAMZA-777
                 URL: https://issues.apache.org/jira/browse/SAMZA-777
             Project: Samza
          Issue Type: Bug
          Components: yarn
    Affects Versions: 0.9.1
            Reporter: Richard Lee
            Priority: Minor


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.



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