Skip to content

Align THV-0038 with horizontal scaling RFC (THV-XXXX)#48

Open
yrobla wants to merge 1 commit intomainfrom
thv-0038-v1
Open

Align THV-0038 with horizontal scaling RFC (THV-XXXX)#48
yrobla wants to merge 1 commit intomainfrom
thv-0038-v1

Conversation

@yrobla
Copy link
Contributor

@yrobla yrobla commented Mar 5, 2026

Update the session-scoped client lifecycle RFC to close the gaps identified during review of the companion horizontal scaling RFC:

  • Expand the metadata layer to include per-backend session IDs (Mcp-Session-Id) and proxyrunner pod URLs, which are required by THV-XXXX to reconstruct vMCP sessions on a different pod without re-initializing backend sessions from scratch
  • Promote backend session IDs from the runtime layer to the metadata layer in the dual-layer table, with a rationale note explaining why they are serializable identifiers and not live connection state
  • Replace "horizontal scaling requires sticky sessions" with "sticky sessions are preferred; Redis-backed storage enables reconstruction at a one-time cost per re-route"
  • Replace the vague "graceful degradation / clients must be recreated" deployment path with the precise reconstruction steps from THV-XXXX (Redis lookup → proxyrunner URL → resume existing backend session)
  • Update Phase 1 implementation plan to specify that per-backend metadata is written to SetData() inside MakeSession() after clients initialize
  • Rename non-goal from "Transparent Horizontal Scaling" to "Sticky-session-free horizontal scaling" and redirect to THV-XXXX
  • Add THV-XXXX as a companion RFC in the References section

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 57088275e1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Update the session-scoped client lifecycle RFC to close the gaps
identified during review of the companion horizontal scaling RFC:

  - Expand the metadata layer to include per-backend session IDs
    (Mcp-Session-Id) and proxyrunner pod URLs, which are required by
    THV-XXXX to reconstruct vMCP sessions on a different pod without
    re-initializing backend sessions from scratch
  - Promote backend session IDs from the runtime layer to the metadata
    layer in the dual-layer table, with a rationale note explaining why
    they are serializable identifiers and not live connection state
  - Replace "horizontal scaling requires sticky sessions" with "sticky
    sessions are preferred; Redis-backed storage enables reconstruction
    at a one-time cost per re-route"
  - Replace the vague "graceful degradation / clients must be recreated"
    deployment path with the precise reconstruction steps from THV-XXXX
    (Redis lookup → proxyrunner URL → resume existing backend session)
  - Update Phase 1 implementation plan to specify that per-backend
    metadata is written to SetData() inside MakeSession() after clients
    initialize
  - Rename non-goal from "Transparent Horizontal Scaling" to
    "Sticky-session-free horizontal scaling" and redirect to THV-XXXX
  - Add THV-XXXX as a companion RFC in the References section
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants