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

FSSchedulerNode is always instantiated with a 0 virtual core capacity

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 2.0.2-alpha
    • Fix Version/s: None
    • Component/s: scheduler
    • Labels:
      None

      Description

      After YARN-2, FSSchedulerNode was not updated to initialize with the underlying RMNode's CPU capacity, and thus always has 0 virtual cores.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                sandyr Sandy Ryza
                Reporter:
                sandyr Sandy Ryza
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: