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

Resource type is ignored when FS decide to preempt

Add voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 3.0.0
    • None
    • fairscheduler
    • None

    Description

      Method Fairscheduler#shouldAttemptPreemption doesn't consider resources other than vcore and memory. We may need to rethink it in the resource type scenario. cc Miklos Szegedi, Wilfred Spiegelenburg and Szilard Nemeth.

          if (context.isPreemptionEnabled()) {
      return (context.getPreemptionUtilizationThreshold() < Math.max(
          (float) rootMetrics.getAllocatedMB() /
              getClusterResource().getMemorySize(),
          (float) rootMetrics.getAllocatedVirtualCores() /
              getClusterResource().getVirtualCores()));
    }

      Attachments

        1. YARN-8059.001.patch
          91 kB
          Szilard Nemeth
        2. YARN-8059.002.patch
          15 kB
          Szilard Nemeth
        3. YARN-8059.003.patch
          25 kB
          Szilard Nemeth
        4. YARN-8059.004.patch
          25 kB
          Szilard Nemeth
        5. YARN-8059.005.patch
          26 kB
          Szilard Nemeth
        6. YARN-8059.006.patch
          67 kB
          Szilard Nemeth

        Issue Links

        depends upon

        Bug - A problem which impairs or prevents the functions of the product. YARN-9019 Ratio calculation of ResourceCalculator implementations could return NaN

        • Major - Major loss of function.
        • Resolved

        Bug - A problem which impairs or prevents the functions of the product. YARN-9025 TestFairScheduler#testChildMaxResources is flaky

        • Major - Major loss of function.
        • Resolved

        Improvement - An improvement or enhancement to an existing feature or task. YARN-8842 Expose metrics for custom resource types in QueueMetrics

        • Major - Major loss of function.
        • Resolved

        Improvement - An improvement or enhancement to an existing feature or task. YARN-8750 Refactor TestQueueMetrics

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Resolved
        is blocked by

        Bug - A problem which impairs or prevents the functions of the product. YARN-9047 FairScheduler: default resource calculator is not resource type aware

        • Major - Major loss of function.
        • Open
        is depended upon by

        Improvement - An improvement or enhancement to an existing feature or task. YARN-5106 Provide a builder interface for FairScheduler allocations for use in tests

        • Major - Major loss of function.
        • Resolved
        relates to

        Improvement - An improvement or enhancement to an existing feature or task. YARN-8842 Expose metrics for custom resource types in QueueMetrics

        • Major - Major loss of function.
        • Resolved

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            snemeth Szilard Nemeth
            yufeigu Yufei Gu
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:

              Slack

                Issue deployment