SPARK-52564 configuration changes not require deleting the checkpoint #51264
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
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?
Why are the changes needed?
Once checkpointing is enabled in Spark Streaming, configuration changes require deleting the checkpoint, which results in loss of state.
code like this:
// Get StreamingContext from checkpoint data or create a new one
val context = StreamingContext.getOrCreate(checkpointDirectory, functionToCreateContext _)
...
context.start()
context.awaitTermination()
I modified the key class org.apache.spark.streaming.StreamingContext by updating the getOrCreate method, so that the latest configurations can be applied when recovering from a checkpoint. This way, there's no need to delete the checkpoint to make configuration changes take effect.
Does this PR introduce any user-facing change?
No
How was this patch tested?
After modifying the Spark source code, I replaced the client-side spark/jars/spark-streaming_2.12-4.0.0.jar. Then, I changed the configuration settings, updating the runtime resources to --num-executors 4 --executor-memory 6G --executor-cores 3. Without touching the checkpoint, I restarted the Spark Streaming application and confirmed that the changes took effect.
Was this patch authored or co-authored using generative AI tooling?
No