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

Try assigning tasks to existing executors by which required resources in ResourceProfile are satisfied

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 3.1.0
    • None
    • Scheduler, Spark Core
    • None

    Description

      By the change in PR of SPARK-29154, submitted tasks are scheduled onto executors only if resource profile IDs strictly match. As a result Spark always starts new executors for customized ResourceProfiles.

      This limitation makes working with process-local jobs unfriendly. E.g. Task cores has been increased from 1 to 4 in a new stage, and executor has 8 slots, it is expected that 2 new tasks can be run on the existing executor but Spark starts new executors for new ResourceProfile. The behavior is unnecessary.

      Attachments

        Issue Links

          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SPARK-27495 SPIP: Support Stage level resource configuration and scheduling

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              zhztheplayer Hongze Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: