Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Today, locality and cpu for the AM can be specified in the AM launch container request but are ignored at the RM. Locality is assumed to be ANY and cpu is dropped. There may be other things too that are ignored. This should be fixed so that the user gets what is specified in their code to launch the AM. cc leftnoteasy vvasudev adhoot
Attachments
Issue Links
- relates to
-
YARN-2005 Blacklisting support for scheduling AMs
- Resolved