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

AbstractYarnScheduler reports the configured maximum resources, instead of the actual, even after the configured waittime

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: scheduler
    • Labels:
      None

      Description

      AbstractYarnScheduler has a configured wait time during which it reports the maximum resources from the configuration instead of the actual resources available in the cluster. However, the first query after the wait time expiration is responded by the configured maximum resources instead of the actual maximum resources. This can result in a app submission to fail with an InvalidResourceRequestException (will attach a unit test in the patch) since the maximum resources reported by the RM is different than the one it sanity checks against at app submission.

        Attachments

        1. YARN-6867.001.patch
          6 kB
          Muhammad Samir Khan

          Issue Links

            Activity

              People

              • Assignee:
                nroberts Nathan Roberts
                Reporter:
                samkhan Muhammad Samir Khan
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: