Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-19373

Mesos implementation of spark.scheduler.minRegisteredResourcesRatio looks at acquired cores rather than registerd cores

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.6.3, 2.0.2, 2.1.0
    • 2.1.1, 2.2.0
    • Mesos
    • None

    Description

      We're currently using `totalCoresAcquired` to account for registered resources, which is incorrect. That variable measures the number of cores the scheduler has accepted. We should be using `totalCoreCount` like the other schedulers do.

      Fixing this is important for locality, since users often want to wait for all executors to come up before scheduling tasks to ensure they get a node-local placement.

      original PR to add support: https://github.com/apache/spark/pull/8672/files

      Attachments

        Activity

          People

            mgummelt Michael Gummelt
            mgummelt Michael Gummelt
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: