bito-code-review[bot] commented on PR #43902: URL: https://github.com/apache/superset/pull/43902#issuecomment-5549390261
<!-- Bito Reply --> The current documentation already describes the trade-off between the default stateless mode and the stateful mode. Specifically, it notes that the default (`True`) allows any pod to handle any request without session affinity, but a client disconnecting mid-tool-call can crash its own session. Setting it to `False` avoids that crash by keeping the transport alive for the session's lifetime, but it mandates session-affinity (sticky session) routing on `Mcp-Session-Id` at the mesh or ingress layer to ensure follow-up requests reach the correct pod. The documentation in `docs/admin_docs/configuration/mcp-server.mdx` covers these implications for operators. **docs/admin_docs/configuration/mcp-server.mdx** ``` | `MCP_STATELESS_HTTP` | `True` | Streamable-HTTP session mode. `True` gives each request a fresh, ephemeral transport, torn down as soon as that request completes; a client disconnecting mid-tool-call can crash its own session. `False` keeps the transport alive for the session's lifetime, avoiding that crash, but requires session-affinity routing on `Mcp-Session-Id` for multi-pod deployments (see [Multi-Pod (Kubernetes)](#multi-pod-kubernetes)). | ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
