[
https://issues.apache.org/jira/browse/SPARK-35714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean R. Owen resolved SPARK-35714.
----------------------------------
Fix Version/s: 3.0.3
3.1.3
3.2.0
Resolution: Fixed
Issue resolved by pull request 32868
[https://github.com/apache/spark/pull/32868]
> Bug fix for deadlock during the executor shutdown
> -------------------------------------------------
>
> Key: SPARK-35714
> URL: https://issues.apache.org/jira/browse/SPARK-35714
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 3.1.2
> Reporter: Wan Kun
> Assignee: Wan Kun
> Priority: Minor
> Fix For: 3.2.0, 3.1.3, 3.0.3
>
> Attachments: three_thread_lock.log
>
>
> When a executor received a TERM signal, it (the second TERM signal) will lock
> java.lang.Shutdown class and then call Shutdown.exit() method to exit the JVM.
> Shutdown will call SparkShutdownHook to shutdown the executor.
> During the executor shutdown phase, RemoteProcessDisconnected event will be
> send to the RPC inbox, and then WorkerWatcher will try to call
> System.exit(-1) again.
> Because java.lang.Shutdown has already locked, a deadlock has occurred.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
