[ZEPPELIN-6256] Fix resource leaks in SparkInterpreterLauncher.detectSparkScalaVersion #5000
+103
−14
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 is this PR for?
This PR fixes resource leaks in the
detectSparkScalaVersion
method ofSparkInterpreterLauncher.java
:These leaks could destabilize Zeppelin over time, especially with frequent interpreter restarts.
What type of PR is it?
Bug Fix
Todos
What is the Jira issue?
How should this be tested?
Unit tests added:
testDetectSparkScalaVersionResourceCleanup
: Verifies that FileInputStream is closed and temporary file is deleted after successful executiontestDetectSparkScalaVersionMultipleCalls
: Ensures no resource accumulation after multiple method invocationsManual testing:
zeppelin-spark*.out
files remainCI: All existing tests pass
Screenshots (if appropriate)
N/A
Questions:
Implementation Details
Code Changes
detectSparkScalaVersion
method to properly manage resources