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

Barrier mode spawns a bunch of threads that get collected on gc

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.4.0
    • 3.0.0
    • Spark Core
    • None

    Description

      After a barrier job is terminated (successfully or interrupted), the accompanying thread created with `Timer` in `BarrierTaskContext` shows in a waiting state until gc is called. We should probably have just one thread to schedule all such tasks, since they just log every 60 seconds.

      Here's a screen shot of the threads growing with more tasks:

      Here's a screen shot of constant number of threads with more tasks:

      Attachments

        Activity

          People

            Unassigned Unassigned
            yogeshgarg yogesh garg
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: