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

ThreadUtils.newDaemonCachedThreadPool(prefix, maxThreadNumber) has unexpected behavior

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.4.1, 1.5.2, 1.6.0
    • 1.4.2, 1.5.3, 1.6.0
    • Spark Core
    • None

    Description

      Currently, ThreadUtils.newDaemonCachedThreadPool(prefix, maxThreadNumber) will throw RejectedExecutionException, if there are already `maxThreadNumber` busy threads and we submit a new task. It's because `SynchronousQueue` cannot cache any task.

      Attachments

        Activity

          People

            zsxwing Shixiong Zhu
            zsxwing Shixiong Zhu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: