-
Notifications
You must be signed in to change notification settings - Fork 425
fix: recover stale MCP sessions after server restart #1418
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
DmarshalTU
wants to merge
6
commits into
kagent-dev:main
Choose a base branch
from
DmarshalTU:fix/graceful_handling
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.
+376
−1
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
b6ba435
fix: recover stale MCP sessions after server restart
DmarshalTU 9ab8f5a
Pull request overview fixes
DmarshalTU 36d80ac
remove adk LivenessProbe and update mcpSessionManager
DmarshalTU 3a3baff
remove mcp health check
DmarshalTU 695d2fa
_close_and_recreate_session
DmarshalTU b283686
apply ruff format
DmarshalTU 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
Oops, something went wrong.
Oops, something went wrong.
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.
my one last concern is the length of these timeouts and the fact that this is added to a normal request path which may create additional latency in the request. If it fails I think we should fail fast and not wait to surface errors to the user.
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.
_PING_TIMEOUT_SECONDS = 1.0
_SESSION_REVALIDATE_TIMEOUT_SECONDS = 2.0?
now:
same block (log warning → try/except around close() → return await super().create_session(headers)) is duplicated for ping failure and for list_tools session-invalid
so your suggestion that create_session:
so there’s one place for prune and recreate”
Did I got you right?
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.
sorry for the late reply, its more so to just shorten those timeouts so we fail fast if there is an error. I think the above timout limits make sense now.