Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Currently a new NM proxy has to be created per container since the secure authentication is using a containertoken from the container.
Attachments
Attachments
Issue Links
- blocks
-
YARN-739 NM startContainer should validate the NodeId
- Closed
- is blocked by
-
YARN-692 Creating NMToken master key on RM and sharing it with NM as a part of RM-NM heartbeat.
- Closed
-
YARN-693 Sending NMToken to AM on allocate call
- Closed
-
YARN-694 Start using NMTokens to authenticate all communication with NM
- Closed
-
YARN-714 AMRM protocol changes for sending NMToken list
- Closed
-
YARN-617 In unsercure mode, AM can fake resource requirements
- Closed
- relates to
-
YARN-575 ContainerManager APIs should be user accessible
- Resolved
-
YARN-718 Remove RemoteUGI.getRemoteUser check from startContainer in ContainerManagerImpl as this is no longer required
- Resolved