Revert "[SPARK-35011][CORE] Avoid Block Manager registrations when StopExecutor msg is in-flight" #33959
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reverts commit b9e53f8.
What changes were proposed in this pull request?
Revert #32114
Why are the changes needed?
It breaks the expected
BlockManager
re-registration (e.g., heartbeat loss of an active executor) due to deferred removal ofBlockManager
, see the check:spark/core/src/main/scala/org/apache/spark/storage/BlockManagerMasterEndpoint.scala
Line 551 in 9cefde8
Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass existing tests.