yuqi1129 opened a new pull request, #14506:
URL: https://github.com/apache/gravitino/pull/14506

   ### What changes were proposed in this pull request?
   
   Configure the Gravitino response read timeout with 
`--gravitino-read-timeout` / `GRAVITINO_READ_TIMEOUT` (default 60 seconds), 
validate finite positive values, and apply it to default, service-identity and 
forwarded-identity clients.
   
   Preserve actionable timeout details through FastMCP, including the method, 
encoded resource path and configured budget. Exclude queries, userinfo, headers 
and body from the new message. Keep the original cause and do not replay 
requests. Authentication subrequests retain their own timeout exception.
   
   ### Why are the changes needed?
   
   HTTPX's implicit five-second read timeout can expire during otherwise valid 
metadata operations, and FastMCP can hide the relevant Gravitino timeout 
context.
   
   Fixes #14498
   
   ### Does this PR introduce _any_ user-facing change?
   
   The default read timeout increases from 5 to 60 seconds; CLI overrides the 
environment variable. Connect, write and pool timeouts remain five seconds. 
This bounds waiting for response data, not total server-operation duration. A 
timed-out mutation may still complete: verify its result before retrying.
   
   ### How was this patch tested?
   
   - All 311 MCP unit tests passed, including a real registered table tool 
through GravitinoMCPServer and its production middleware, all identity paths, 
configuration precedence, no replay, sanitized diagnostics, cause preservation 
and OAuth timeout isolation.
   - Reinstating the five-second client timeout makes both configuration-wiring 
regressions fail; restoring the implementation passes the suite.
   - Black/isort, full MCP pylint and RAT passed. Independent fresh-context 
review found no outstanding findings.
   - No live slow-network, external IdP or third-party MCP client budget test 
was run; MockTransport injects timeout errors and separate assertions verify 
client budgets.
   


-- 
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]

Reply via email to