[
https://issues.apache.org/jira/browse/SPARK-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130978#comment-14130978
]
Apache Spark commented on SPARK-3495:
-------------------------------------
User 'tdas' has created a pull request for this issue:
https://github.com/apache/spark/pull/2366
> Block replication fails continuously when the replication target node is dead
> -----------------------------------------------------------------------------
>
> Key: SPARK-3495
> URL: https://issues.apache.org/jira/browse/SPARK-3495
> 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
>
> If a block manager (say, A) wants to replicate a block and the node chosen
> for replication (say, B) is dead, then the attempt to send the block to B
> fails. However, this continues to fail indefinitely. Even if the driver
> learns about the demise of the B, A continues to try replicating to B and
> failing miserably.
> The reason behind this bug is that A initially fetches a list of peers from
> the driver (when B was active), but never updates it after B is dead. This
> affects Spark Streaming as its receiver uses block replication.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
