hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-1915) ClientToAMTokenMasterKey should be provided to AM at launch time
Date Fri, 17 Oct 2014 13:05:34 GMT

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

Jason Lowe updated YARN-1915:
-----------------------------
    Priority: Blocker  (was: Critical)

Per offline discussion with [~vinodkv] marking this as a blocker for 2.6.

> ClientToAMTokenMasterKey should be provided to AM at launch time
> ----------------------------------------------------------------
>
>                 Key: YARN-1915
>                 URL: https://issues.apache.org/jira/browse/YARN-1915
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>    Affects Versions: 2.2.0
>            Reporter: Hitesh Shah
>            Assignee: Jason Lowe
>            Priority: Blocker
>         Attachments: YARN-1915.patch, YARN-1915v2.patch, YARN-1915v3.patch
>
>
> Currently, the AM receives the key as part of registration. This introduces a race where
a client can connect to the AM when the AM has not received the key. 
> Current Flow:
> 1) AM needs to start the client listening service in order to get host:port and send
it to the RM as part of registration
> 2) RM gets the port info in register() and transitions the app to RUNNING. Responds back
with client secret to AM.
> 3) User asks RM for client token. Gets it and pings the AM. AM hasn't received client
secret from RM and so RPC itself rejects the request.



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

Mime
View raw message