Repository navigation
docs(mcp): timeout and retry settings (ENG-3329) - #345
harshranjan-ftw wants to merge 1 commit into
Conversation
…ENG-3329) Signed-off-by: Harsh Ranjan <harsh.ranjan@hydradb.com>
✅ Mintlify HygieneNo issues found. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
✅ OpenHack SummarySecurity review of docs(mcp): timeout and retry settings (ENG-3329). 1 changed file; 0 findings at or above the low reporting threshold. Confidence Score: 5/5No reportable security findings were detected in this scan. Security merge-readiness rubric: 1 = critical, 2 = high, 3 = medium, 4 = low, 5 = no reportable findings. This score reflects scan findings, not a guarantee of correctness or complete coverage. Files Needing Attention: None Important Files Changed
Last reviewed commit: 603534a · View review on OpenHack
|
[Low impact] The documentation appears safe to merge once the author's stated MCP release prerequisite is met. SummaryAdds timeout and retry guidance to
Reviews (1) · Last reviewed commit: "docs(mcp): timeout and retry settings, a..." · Reviewed by Greptile |
tushar-hydradb
left a comment
There was a problem hiding this comment.
didn't review thoroughly, approving to unblock. tested per https://hydradb.slack.com/archives/C0BA3AEHPPZ/p1793627799017369?thread_ts=1793579113.482719&cid=C0BA3AEHPPZ
What
Linear: ENG-3329
The MCP page did not list the timeout and retry settings. They were only in the MCP repo's README. This PR adds them to the environment-variable table and adds a short "Timeouts and retries" section. The section explains the whole-call deadline, which writes are not retried after an unclear failure,
Retry-After, and cancellation.Changes
plugins/mcp.mdx:HYDRADB_TIMEOUT_SECONDS(default 45) andHYDRADB_MAX_RETRIES(default 2) in the environment-variable table, plus a new "Timeouts and retries" section under Configuration.Testing
mintlify-hygiene check --deny-warnings: passed.Merge order
Need help on this PR? Tag
@codesmith-botwith what you need.