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 2014/11/10 23:33:33 UTC
[jira] [Commented] (SPARK-3496) Block replication can by mistake
choose driver BlockManager as a peer for replication
[ https://issues.apache.org/jira/browse/SPARK-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14205439#comment-14205439 ]
Apache Spark commented on SPARK-3496:
-------------------------------------
User 'tdas' has created a pull request for this issue:
https://github.com/apache/spark/pull/3191
> Block replication can by mistake choose driver BlockManager as a peer for replication
> -------------------------------------------------------------------------------------
>
> Key: SPARK-3496
> URL: https://issues.apache.org/jira/browse/SPARK-3496
> Project: Spark
> Issue Type: Bug
> Components: Block Manager, Spark Core, Streaming
> Affects Versions: 1.0.2, 1.1.0
> Reporter: Tathagata Das
> Assignee: Tathagata Das
> Priority: Critical
> Fix For: 1.2.0
>
>
> When selecting peer block managers for replicating a block, the driver block manager can also get chosen accidentally. This is because BlockManagerMasterActor did not filter out the driver block manager.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org