Details
-
Sub-task
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
-
Reviewed
Description
Without security, it is impossible to completely avoid AMs faking resources. We can at the least make it as difficult as possible by using the same container tokens and the RM-NM shared key mechanism over unauthenticated RM-NM channel.
In the minimum, this will avoid accidental bugs in AMs in unsecure mode.
Attachments
Attachments
Issue Links
- blocks
-
YARN-613 Create NM proxy per NM instead of per container
- Closed
- breaks
-
MAPREDUCE-5257 TestContainerLauncherImpl fails
- Closed
-
MAPREDUCE-5261 TestRMContainerAllocator is exiting and failing the build
- Closed
- is blocked by
-
YARN-582 Restore appToken and clientToken for app attempt after RM restart
- Closed
- is related to
-
YARN-713 ResourceManager can exit unexpectedly if DNS is unavailable
- Closed