Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-11011

Make YARN Router throw Exception to client clearly

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 3.3.1
    • 3.4.0
    • yarn

    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.

      Attachments

        1. router-error.png
          169 kB
          Yuan Luo

        Issue Links

          Activity

            People

              Unassigned Unassigned
              luoyuan Yuan Luo
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m