[YARN-1915] ClientToAMTokenMasterKey should be provided to AM at launch time

• Type: Sub-task
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 2.6.0
• Target Version/s: 2.6.0
• Hadoop Flags: Reviewed
• Assignee: Jason Darrell Lowe
• Reporter: Hitesh Shah
• Created: 08/Apr/14 22:50
• Updated: 01/Dec/14 03:08
• Resolved: 25/Oct/14 05:51

Description

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.

Issue Links

• is broken by: YARN-610 ClientToken (ClientToAMToken) should not be set in the environment
• relates to: TEZ-1030 Address intermittent errors created due to race condition in YARN-1915