Restrict topology scheduler strategies to the shipped strategies when no allowlist is configured - #8986
Open
rzo1 wants to merge 1 commit into
Open
Restrict topology scheduler strategies to the shipped strategies when no allowlist is configured#8986rzo1 wants to merge 1 commit into
rzo1 wants to merge 1 commit into
Conversation
… no allowlist is configured
reiabreu
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.
nimbus.scheduler.strategy.class.whitelisthad no entry inconf/defaults.yaml, andReflectionUtils.newSchedulerStrategyInstancetreated an unset list as "allow any class", so Nimbus instantiated whatever class a topology named intopology.scheduler.strategy.Unset now means the six strategies that ship with Storm. An explicitly configured list, including an empty one, is honoured unchanged.
Behaviour change: a cluster running an out-of-tree strategy with no allowlist configured will start failing scheduling for those topologies. The exception previously carried no message at all and now names the refused class and the config key to add. Adds
ReflectionUtilsTest.