Repository navigation
Stop retrying timed-out Ollama generations; wait 30 minutes - #268
Merged
Merged
Conversation
A 27B model on a ~137 KB payload was hitting the 5-minute HTTP timeout. urllib3 then retried the same /chat/completions call, so Ollama kept "still processing" while history stayed Pending. Local providers now use a 30-minute read timeout, no read-timeout retries, status=processing, and the UI polls for 30 minutes.
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
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.
Logs showed ReadTimeoutError at 300s then urllib3 retrying the same chat/completions request, which restarts Ollama. Local-openai now waits 30 minutes, does not retry a live generation, and marks the job Processing.