You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "wuyi (Jira)" <ji...@apache.org> on 2021/09/13 02:35:00 UTC
[jira] [Resolved] (SPARK-36700) BlockManager re-registration is
broken due to deferred removal of BlockManager
[ https://issues.apache.org/jira/browse/SPARK-36700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
wuyi resolved SPARK-36700.
--------------------------
Fix Version/s: 3.3.0
3.0.4
3.1.3
3.2.0
Assignee: wuyi
Resolution: Fixed
> BlockManager re-registration is broken due to deferred removal of BlockManager
> -------------------------------------------------------------------------------
>
> Key: SPARK-36700
> URL: https://issues.apache.org/jira/browse/SPARK-36700
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 3.0.3, 3.1.2, 3.2.0, 3.3.0
> Reporter: wuyi
> Assignee: wuyi
> Priority: Blocker
> Fix For: 3.2.0, 3.1.3, 3.0.4, 3.3.0
>
>
> Due to the deferred removal of BlockManager (introduced in SPARK-35011), an expected BlockManager re-registration could be refused as the inactive BlockManager still exists in the map `blockManagerInfo`:
> https://github.com/apache/spark/blob/9cefde8db373a3433b7e3ce328e4a2ce83b1aca2/core/src/main/scala/org/apache/spark/storage/BlockManagerMasterEndpoint.scala#L551
--
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