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 2018/09/09 11:35:00 UTC
[jira] [Commented] (SPARK-25386) Don't need to synchronize the
IndexShuffleBlockResolver for each writeIndexFileAndCommit
[ https://issues.apache.org/jira/browse/SPARK-25386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608426#comment-16608426 ]
Apache Spark commented on SPARK-25386:
--------------------------------------
User 'ConeyLiu' has created a pull request for this issue:
https://github.com/apache/spark/pull/22371
> Don't need to synchronize the IndexShuffleBlockResolver for each writeIndexFileAndCommit
> ----------------------------------------------------------------------------------------
>
> Key: SPARK-25386
> URL: https://issues.apache.org/jira/browse/SPARK-25386
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 2.3.1
> Reporter: Xianyang Liu
> Priority: Major
>
> Now, we need synchronize the instance of IndexShuffleBlockResolver in order to make the commit check and tmp file rename atomically. This can be improved. We could synchronize a lock which is different for each `shuffleId + mapId` instead of synchronize the indexShuffleBlockResolver for each writeIndexFileAndCommit.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org