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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SPARK-31922][CORE] logDebug "RpcEnv already stopped" error on LocalSparkCluster shutdown #28746
[SPARK-31922][CORE] logDebug "RpcEnv already stopped" error on LocalSparkCluster shutdown #28746
Changes from 7 commits
d2555c2
db435d2
7a713ac
09bbb03
092c442
ef576c0
4c8ceec
59a0595
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change fixes the failure of test
org.apache.spark.launcher.LauncherBackendSuite.standalone/client: launcher handle
. After sleeping one more second, the application launched by theSparkLauncher
now has a chance to submit tasks to TaskScheduler and callreviveOffers
on the SchedulerBackend. At the same time, theSparkLauncher
will ask the application to stop. Therefore, the SchedulerBackend could have been already stopped when it receivesReviveOffers
messages, which would fail the entire application at the end.So, I use
Utils.tryLogNonFatalError
to fix it and I think this should be fine since we've already use it at:spark/core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
Lines 137 to 139 in c560428