You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (Jira)" <ji...@apache.org> on 2020/06/28 14:32:00 UTC
[jira] [Commented] (SPARK-32118) Use fine-grained read write lock
for each database in HiveExternalCatalog
[ https://issues.apache.org/jira/browse/SPARK-32118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147353#comment-17147353 ]
Apache Spark commented on SPARK-32118:
--------------------------------------
User 'LantaoJin' has created a pull request for this issue:
https://github.com/apache/spark/pull/28938
> Use fine-grained read write lock for each database in HiveExternalCatalog
> -------------------------------------------------------------------------
>
> Key: SPARK-32118
> URL: https://issues.apache.org/jira/browse/SPARK-32118
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.0.0, 3.1.0
> Reporter: Lantao Jin
> Priority: Major
>
> In HiveExternalCatalog, all metastore operations are synchronized by a same object lock. In a heavy traffic Spark thriftserver or Spark Driver, users's queries may be stuck by any a long operation. For example, if a user is accessing a table which contains mass partitions, the operation loadDynamicPartitions() holds the object lock for a long time. All queries are blocking to wait for the lock.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org