Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.3.1
-
Reviewed
Description
When router submits job to yarn, the job is rejected by yarn for some reason. Yarn router just throw exception to log and return not enough info to client.
The router always throws the following non-obvious error to client:
Exception in thread "main" org.apache.hadoop.yarn.server.federation.policies.exceptions.FederationPolicyException:
No active SubCluster available to submit the request.
To make it easy for the user to locate the cause of a job submission failure, we need to make Router throw the true cause of the error to the client clearly.
