fix(distributed): reload changed model context - #11567
Open
localai-org-maint-bot wants to merge 1 commit into
Open
fix(distributed): reload changed model context#11567localai-org-maint-bot wants to merge 1 commit into
localai-org-maint-bot wants to merge 1 commit into
Conversation
Distributed routing reused a warm worker by model ID even when the model context changed. The worker kept its original context and truncated requests at that old limit. Retire an idle replica when its stored context differs. The existing cold-load path then starts that replica with the current model options. Assisted-by: Codex:gpt-5
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
1 participant
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.
Description
This PR fixes #11566.
Distributed routing reused a warm worker by model ID even when the model context changed. An idle replica now compares its persisted load context with the current model options. When they differ, the router retires that exact replica and uses the existing cold-load path to recreate it with the configured context.
Busy replicas and legacy registry rows without stored options remain untouched.
Notes for Reviewers
Focused verification:
The full
go test ./core/services/nodes -count=1run reached 255 passing specs, but 217 database-backed specs could not start because this cron environment has no rootless Docker/Postgres provider.Signed commits