[SPARK-54489][CORE] Avoid returning corrupted Kryo objects #53193
+19
−3
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?
When
Kryo.writeClassAndObjectthrows aNegativeArraySizeException, the Kryo instance shall no longer be returned to the pool.Why are the changes needed?
https://github.com/EsotericSoftware/kryo/pull/1198When Kryo.writeClassAndObject fails to resize, it throws a
NegativeArraySizeException.Spark then returns this Kryo instance to the pool. The next time this object is reused, it will always throw an
ArrayIndexOutOfBoundsException.Simple test
Does this PR introduce any user-facing change?
No
How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?
No