hadoop-yarn-issues mailing list archives

[jira] [Commented] (YARN-1915) ClientToAMTokenMasterKey should be provided to AM at launch time

Date

Wed, 13 Aug 2014 18:04:12 GMT

[ https://issues.apache.org/jira/browse/YARN-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14095820#comment-14095820
]
Daryn Sharp commented on YARN-1915:
-----------------------------------
I suspect it's because it removes the burden from the AM to strip the secret from the credentials
so it doesn't leak to other processes.
> 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: Critical
> Attachments: YARN-1915.patch, YARN-1915v2.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.2#6252)