-
Notifications
You must be signed in to change notification settings - Fork 472
mcp: retry transient errors on SSE reconnect #1027
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
aditya-786
wants to merge
2
commits into
modelcontextprotocol:main
Choose a base branch
from
aditya-786:fix/streamable-sse-transient-retry
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+105
−13
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why did you decide to reset reconnectDelay ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reconnectDelayhere is the delay the server asked for via the SSEretry:field on the stream that just ended (processStreamreads it out of that field). It is a one-shot hint tied to that specific stream, so I honor it on the first reconnect attempt.Once the reconnect actually connects but the server rejects it transiently (
ErrRejected) and we loop back to retry, there is no freshretry:value for those in-loop attempts. Continuing to pass the old one would re-apply that same server delay on every retry, even though it belonged to the previous stream. Zeroing it letsconnectSSEfall back tocalculateReconnectDelay, which is the normal jittered exponential backoff.It does not become a no-delay busy loop:
connectSSEruns withinitial=false, soattemptstarts at 1 anddelay = calculateReconnectDelay(1)(a real backoff); passingreconnectDelay == 0just means we no longer override that. TheretriesWithoutProgress > maxRetriescap bounds the loop overall.Happy to add a one-line comment on that line to spell out the intent if it reads as surprising.