[
https://issues.apache.org/jira/browse/SPARK-49544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyukjin Kwon resolved SPARK-49544.
----------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
Issue resolved by pull request 48034
[https://github.com/apache/spark/pull/48034]
> Severe lock contention in SparkConnectExecutionManager
> ------------------------------------------------------
>
> Key: SPARK-49544
> URL: https://issues.apache.org/jira/browse/SPARK-49544
> Project: Spark
> Issue Type: Improvement
> Components: Connect
> Affects Versions: 4.0.0
> Reporter: Changgyoo Park
> Assignee: Changgyoo Park
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
>
> Critical sections protected by executionsLock can become too broad when there
> are too many ExecuteHolders, e.g., >= 10^4. The problem is aggravated when
> there are too many threads in the system: priority inversion. In order to
> minimise the chance of a thread getting pre-empted holding executionsLock,
> replace it with a concurrent hash map that internally partitions the data:
> coarse-grained locking -> fine-grained locking.
> -> https://issues.apache.org/jira/browse/SPARK-49580 will be eventually
> needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
