If a queue is configured with maxResources set to 0 for a resource, and an application is submitted to that queue that requests that resource, that application will remain pending until it is removed or moved to a different queue. This behavior can be realized without extended resources, but it’s unlikely a user will create a queue that allows 0 memory or CPU. As the number of resources in the system increases, this scenario will become more common, and it will become harder to recognize these cases. Therefore, the scheduler should indicate in the diagnostic string for an application if it was not scheduled because of a 0 maxResources setting.
Example configuration (fair-scheduler.xml) :
The job hangs and the application diagnostic info is empty.
Given that an exception is thrown before any mapper/reducer container is created, the diagnostic message of the AM should be updated.