Description
The client side does not show enough information on why the job failed. Here is step to reproduce it:
1) set the scheduler to be capacity scheduler with queues a, b
2) submit a job to a queue that is not a,b
The job just fails without saying why it failed. We should have enough trace log at the client side to let the user know why it failed.
Attachments
Attachments
Issue Links
- blocks
-
MAPREDUCE-2952 Application failure diagnostics are not consumed in a couple of cases
- Closed
- breaks
-
MAPREDUCE-2975 ResourceManager Delegate is not getting initialized with yarn-site.xml as default configuration.
- Closed