Require Kryo class registration in the state serializer - #8990
Merged
Conversation
Registration is keyed off topology.fall.back.on.java.serialization, matching the tuple path in DefaultKryoFactory. Registers the types Storm persists without the component declaring them (byte[], CheckPointState), after the configured registrations so their ids are unaffected. Clears the class resolver's name caches on reset: Kryo skips that when registration is required, which would desynchronise a second read of state written by an earlier release.
GGraziadei
force-pushed
the
kryo-register-internal-classes
branch
from
August 21, 2026 18:04
93f9837 to
0185b58
Compare
rzo1
approved these changes
Aug 22, 2026
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
2 participants
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.
Controlled by topology.fall.back.on.java.serialization and aligned with the tuple path in DefaultKryoFactory, this mechanism registers core storm-persisted types (byte[], CheckPointState) without requiring component-level declarations. It also clears class resolver name caches on reset to maintain readability for state generated by earlier releases.