Skip to content
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.

Sign up for GitHub

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-51048][CORE] Support stop java spark context with exit code #49746

Closed
wants to merge 5 commits into from
Closed

[SPARK-51048][CORE] Support stop java spark context with exit code #49746

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
9c24ba9
SPARK-51048 | Support stop java spark context with exit code
prathit06 Jan 31, 2025
bab84b8
SPARK-51048 | Support stop java spark context with exit code
prathit06 Feb 3, 2025
b500324
SPARK-51048 | Support stop java spark context with exit code
prathit06 Feb 3, 2025
68d4c33
SPARK-51048 | Support stop java spark context with exit code
prathit06 Feb 3, 2025
2cce3c3
SPARK-51048 | updated javadoc
prathit06 Feb 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions core/src/main/scala/org/apache/spark/api/java/JavaSparkContext.scala
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -552,6 +552,21 @@ class JavaSparkContext(val sc: SparkContext) extends Closeable {
sc.stop()
}

/**
* Shut down the SparkContext with exit code that will passed to scheduler backend.
* In client mode, client side may call `SparkContext.stop()` to clean up but exit with
* code not equal to 0. This behavior cause resource scheduler such as `ApplicationMaster`
* exit with success status but client side exited with failed status. Spark can call
* this method to stop SparkContext and pass client side correct exit code to scheduler backend.
* Then scheduler backend should send the exit code to corresponding resource scheduler
* to keep consistent.
*
* @param exitCode Specified exit code that will passed to scheduler backend in client mode.
*/
def stop(exitCode: Int): Unit = {
sc.stop(exitCode)
}

override def close(): Unit = stop()

/**
Expand Down