[
https://issues.apache.org/jira/browse/SPARK-36700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413865#comment-17413865
]
wuyi commented on SPARK-36700:
------------------------------
Reverted by [https://github.com/apache/spark/pull/33942] and backported to 3.2,
3.1, 3.0.
> 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
> Priority: Blocker
>
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
