hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-2031) YARN Proxy model doesn't support REST APIs in AMs
Date Mon, 16 Feb 2015 18:35:12 GMT

     [ https://issues.apache.org/jira/browse/YARN-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Steve Loughran updated YARN-2031:
    Attachment: YARN-2031-002.patch

This is an iteration which implements part of the feature; not complete but posted for interim

# The AmIPFilter now redirects with the relevant verb, as tested
# The proxy is lined up for it, except that it still only registers support for GET.
# the redirect code in ProxyUtils is now method aware.

There's some complexity in the proxy related to policy related to redirects to YARN pages
& user click throughs.

h3. Click throughs:

How to handle the "click through" warning on non GET operations. Current policy: reject with
401. The warn logic could also probe the accepted types of the GET, and 401 on anything that
wanted XML or JSON, so app apis would fail fast. Thoughts?

h3. redirecting to "RM pages" vs "app pages"

RM pages are:the app-not-registered redirect to the RM page, or the app completed redirect
to the logs

For GET operations, these are redirected as today, with a 302.

For other verbs, a 404 on the original URL Is being returned. This is designed to fail when
an app isn't running, either not-started or completed. 

> YARN Proxy model doesn't support REST APIs in AMs
> -------------------------------------------------
>                 Key: YARN-2031
>                 URL: https://issues.apache.org/jira/browse/YARN-2031
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>    Affects Versions: 2.4.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>         Attachments: YARN-2031-002.patch, YARN-2031.patch.001
> AMs can't support REST APIs because
> # the AM filter redirects all requests to the proxy with a 302 response (not 307)
> # the proxy doesn't forward PUT/POST/DELETE verbs
> Either the AM filter needs to return 307 and the proxy to forward the verbs, or Am filter
should not filter a REST bit of the web site

This message was sent by Atlassian JIRA

View raw message