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

Job cancellation causes py4j errors on Jupyter due to pinned thread mode

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • 3.2.0
    • 3.2.1, 3.3.0
    • PySpark
    • None

    Description

      Spark 3.2.0 turned on py4j pinned thread mode by default (SPARK-35303). However, in a jupyter notebook, after I cancel (interrupt) a long-running Spark job, the next Spark command will fail with some py4j errors. See attached notebook for repro.

      Cannot reproduce the issue after I turn off pinned thread mode .

      Attachments

        1. pinned.ipynb
          18 kB
          Xiangrui Meng

        Issue Links

          is caused by

          Bug - A problem which impairs or prevents the functions of the product. SPARK-35303 Enable pinned thread mode by default

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

          Pull request #34814 [Github] Pull Request #34814 (HyukjinKwon)

          Pull request #34814 [Github] Pull Request #34814 (HyukjinKwon)

          Activity

            People

              gurwls223 Hyukjin Kwon
              mengxr Xiangrui Meng
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: