[
https://issues.apache.org/jira/browse/SPARK-46861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dongjoon Hyun resolved SPARK-46861.
-----------------------------------
Fix Version/s: 3.4.3
3.5.1
4.0.0
Resolution: Fixed
Issue resolved by pull request 44882
[https://github.com/apache/spark/pull/44882]
> Potential Deadlock in DAGScheduler
> ----------------------------------
>
> Key: SPARK-46861
> URL: https://issues.apache.org/jira/browse/SPARK-46861
> Project: Spark
> Issue Type: Bug
> Components: Scheduler
> Affects Versions: 4.0.0, 3.5.1, 3.4.3
> Reporter: Fredrik Klauß
> Assignee: Fredrik Klauß
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.3, 3.5.1, 4.0.0
>
>
> * The DAGScheduler could currently run into a deadlock with another thread if
> both access the partitions of the same RDD at the same time.
> * To make progress in getCacheLocs, we require both exclusive access to the
> RDD partitions and the location cache. We first lock on the location cache,
> and then on the RDD.
> * When accessing partitions of an RDD, the RDD first acquires exclusive
> access on the partitions, and then might acquire exclusive access on the
> location cache.
> * If thread 1 is able to acquire access on the RDD, while thread 2 holds the
> access to the location cache, we can run into a deadlock situation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
