[SPARK-55974][CORE][YARN] Relaunch new executors if the executor launching take too long time#54771
Open
AngersZhuuuu wants to merge 3 commits intoapache:masterfrom
Open
[SPARK-55974][CORE][YARN] Relaunch new executors if the executor launching take too long time#54771AngersZhuuuu wants to merge 3 commits intoapache:masterfrom
AngersZhuuuu wants to merge 3 commits intoapache:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changes were proposed in this pull request?
This PR adds executor launch timeout tracking and automatic relaunch for YARN mode. When an executor takes too long to register with the driver after its container is allocated, the Application Master (AM) will treat it as stuck and request replacement containers.
Why are the changes needed?
In YARN mode, executors can get stuck during launch (e.g., slow node, resource contention, network issues). Without a timeout, the AM keeps waiting indefinitely, which can:
This change adds a configurable timeout so the AM can detect stuck launches and request replacement executors, improving reliability and resource utilization.
Does this PR introduce any user-facing change?
Yes. A new configuration is introduced:spark.yarn.containerLaunchTimeout (default: 10min)
How was this patch tested?
Added UT
Was this patch authored or co-authored using generative AI tooling?
No