[SPARK-30355][CORE] Unify isExecutorActive between CoarseGrainedSchedulerBackend and DriverEndpoint #27012
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?
Unify
DriverEndpoint. executorIsAlive()
andCoarseGrainedSchedulerBackend .isExecutorActive()
.Why are the changes needed?
DriverEndPoint
has methodexecutorIsAlive()
to check wether an executor is alive/active, whileCoarseGrainedSchedulerBackend
has methodisExecutorActive()
to do the same work. But,isExecutorActive()
seems forget to considerexecutorsPendingLossReason
. Unify these two methods makes behavior be consistent betweenDriverEndPoint
andCoarseGrainedSchedulerBackend
and make code more easier to maintain.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass Jenkins.