# Doc site updates — May 2026 **URL:** \ **Category:** Using FoundationDB\ **Created:** [May 8, 2026, 9:23am UTC](https://forums.foundationdb.org/t/doc-site-updates-may-2026/5241 "2026-05-08T09:23:06Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![panghy](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/panghy/32/19_2.png) [@panghy](https://forums.foundationdb.org/u/panghy)\ **Post date:** [May 8, 2026, 9:23am UTC](https://forums.foundationdb.org/t/doc-site-updates-may-2026/5241/1 "2026-05-08T09:23:06Z")
Hey all, A couple of doc site updates from this month’s open source working group meeting: - **Gray failure detection** — promoted from a two-line passing mention to a proper [operations guide](https://foundationdb.vercel.app/operations/gray-failure-detection/), and now framed as a **recommended production setting** in suggest-only mode (paralleling how `causal_read_risky` is documented). The page covers the worker peer monitor, cluster-controller aggregation, the full knob inventory, trace events to watch, and a safe pre-prod → recovery → failover rollout. 7.4-only additions like the `gray_failure` section in `status json` (`CC_GRAY_FAILURE_STATUS_JSON`), the SS-complaint opt-ins, and the `CC_ENABLE_REMOTE_LOG_ROUTER_*` knob split are called out per-version. Also cross-linked from the Configuration page so it’s discoverable next to other production-recommended toggles. - **What’s Next / 8.0 preview page** — new [Roadmap page](https://foundationdb.vercel.app/getting-started/roadmap/) covering work that has landed in `apple/foundationdb` `main` but is not yet in any released 7.3.x / 7.4.x build. Top-of-page admonition is explicit that no public 8.0 build exists today. Items tracked: Stable / Cluster Health Metric (apple/foundationdb#12899), more aggressive region failover via `CC_FAILOVER_DUE_TO_TPS_LIMIT_DURATION` (#12849), faster GRV rejection via `max_grv_queue_delay` + `transaction_grv_queue_rejected` (#13085), VersionedMap optimization (#13028). Feedback welcome — especially if anything looks off, or if you’d like the roadmap page to track more items. ---
**Author:** ![domenic](https://avatars.discourse-cdn.com/v4/letter/d/da6949/32.png) [@domenic](https://forums.foundationdb.org/u/domenic)\ **Post date:** [May 9, 2026, 8:28am UTC](https://forums.foundationdb.org/t/doc-site-updates-may-2026/5241/2 "2026-05-09T08:28:55Z")
Hi there, Thanks a lot for the update. I just saw the website for the first time. It looks great, thanks a lot for the effort you have put into it. I observed two things: 1. The invitation link to the Discord server has expired. 2. On [this site](https://foundationdb.vercel.app/7.3/getting-started/versions/#storage-engine-names), I noticed that the feature GetMappedRange is not flagged as experimental. Has it become stable? In all the docs I could find, as well as in the Java SDK (which I use), the feature is still marked as experimental. Maybe I missed something. Have a great day Domenic ---
**Author:** ![panghy](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/panghy/32/19_2.png) [@panghy](https://forums.foundationdb.org/u/panghy)\ **Post date:** [May 10, 2026, 3:18am UTC](https://forums.foundationdb.org/t/doc-site-updates-may-2026/5241/3 "2026-05-10T03:18:44Z")
Sorry, yeah GetMappedRange is still experimental: > > > \## Summary > > GetMappedRange is still flagged as experimental upstream in all curr…ently-built FoundationDB versions (7.1, 7.3, 7.4), but the doc site was presenting it as a regular shipped feature. This PR brings the docs in line with upstream. > > \## Upstream evidence > > \- Java \`ReadTransaction.getMappedRange\` Javadoc on both \[\`release-7.3\`\](https://github.com/apple/foundationdb/blob/release-7.3/bindings/java/src/main/com/apple/foundationdb/ReadTransaction.java) and \[\`release-7.4\`\](https://github.com/apple/foundationdb/blob/release-7.4/bindings/java/src/main/com/apple/foundationdb/ReadTransaction.java): \*"WARNING: This feature is considered experimental at this time. It is only allowed when using snapshot isolation AND disabling read-your-writes."\* > \- Upstream issue \[apple/foundationdb#11133\](https://github.com/apple/foundationdb/issues/11133): maintainer \`@jzhou77\` confirmed GetMappedRange remains experimental in 7.3. > \- 7.4 release notes mention only a bug fix (PR #10522) for GetMappedRange — no graduation to stable. > \- Apple's published Python API reference (apple.github.io/foundationdb, 7.3.77) does not document \`get\_mapped\_range\` at all. > > \## Changes > > | File | Change | > |---|---| > | \`docs/api/python.md\` | \`!!! info\` → \`!!! warning "Experimental"\`; example now uses \`tr.options.set\_read\_your\_writes\_disable()\` + \`tr.snapshot.get\_mapped\_range(...)\` to match the upstream requirement. | > | \`docs/getting-started/versions.md\` | 7.1 highlights bullet + Feature Availability Matrix row marked \`(experimental)\` in all 3 columns. | > | \`docs/getting-started/index.md\` | 7.1 highlights bullet gets \`{{ version\_pill("7.1", "experimental") }}\`. | > | \`docs/getting-started/quickstart.md\` | 7.1 tip notes experimental + snapshot/RYW-disable requirement. | > | \`docs/getting-started/first-app.md\` | Same as quickstart. | > > \## Verification > > \`\`\`bash > for v in 7.1 7.3 7.4; do FDB\_VERSION=$v mkdocs build --strict || echo FAILED-$v; done > \`\`\` > > All three versions build cleanly with \`--strict\`. The 7.1 build of \`docs/getting-started/index.md\` renders the \`EXPERIMENTAL\` pill on the GetMappedRange bullet; the 7.1, 7.3, and 7.4 builds of \`docs/api/python.md\` render the warning admonition. > > \## Out of scope > > \- New dedicated GetMappedRange feature page. > \- Auditing other experimental features (Tenants, ChangeFeed, MetaCluster, idempotent txn) — tracked separately in upstream issue #11133. > > > \--- > Pull Request opened by \[Augment Code\](https://www.augmentcode.com/) with guidance from the PR author ---
**Author:** ![panghy](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/panghy/32/19_2.png) [@panghy](https://forums.foundationdb.org/u/panghy)\ **Post date:** [May 10, 2026, 5:45am UTC](https://forums.foundationdb.org/t/doc-site-updates-may-2026/5241/4 "2026-05-10T05:45:20Z")
Discord fix: > > > \## Summary > > The Discord invite \`https://discord.gg/foundationdb\` had expired (va…nity URLs depend on the server holding Boost Level 3). This PR swaps in the new permanent invite (\`https://discord.gg/n5eW5cwPBc\`) and centralizes the URL so future rotations are a 2-file edit instead of a multi-file content sweep. > > \## Changes > > \- \*\*\`main\_hooks.py\`\*\* — added a module-level \`DISCORD\_INVITE\` constant exported as the \`discord\_invite\` Jinja variable for all built versions. > \- \*\*4 markdown references\*\* — replaced hard-coded \`https://discord.gg/foundationdb\` with \`{{ discord\_invite }}\`: > - \`docs/index.md\` > - \`docs/community/index.md\` (×2) > - \`docs/community/contributing.md\` > \- \*\*\`mkdocs.yml\`\*\* — replaced the social-icons link literal with the new invite. (mkdocs.yml is parsed before the macros plugin runs, so it cannot use the Jinja variable; this stays a literal.) > \- \*\*\`AGENTS.md\`\*\* — added a new "Rotating the Discord invite" section (with TOC entry) documenting that future rotations require updating both \`main\_hooks.py\` and \`mkdocs.yml\`. > > \## Verification > > \- ✅ Zero \`discord.gg/foundationdb\` matches remaining anywhere in the repo or rendered \`site/\`. > \- ✅ \`discord\_invite\` resolves to the new URL for all three FDB versions. > \- ✅ \`mkdocs build --strict\` passes for 7.1, 7.3, and 7.4. > \- ✅ Rendered HTML on the home, community, and contributing pages contains the new invite across all three builds. > \- ✅ Footer social icon points to the new invite. > > \## Long-run > > If the new vanity URL also breaks at some point, the rotation procedure is now documented in AGENTS.md and lives in two known files. If we want stronger insulation against future breakage, a follow-up could add a \`docs/community/discord.md\` redirect page or a Vercel-level redirect — intentionally out of scope here. > > \--- > Pull Request opened by \[Augment Code\](https://www.augmentcode.com/) with guidance from the PR author ---
**Author:** ![RossWilliams](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/rosswilliams/32/1996_2.png) [@RossWilliams](https://forums.foundationdb.org/u/RossWilliams)\ **Post date:** [May 11, 2026, 3:49pm UTC](https://forums.foundationdb.org/t/doc-site-updates-may-2026/5241/5 "2026-05-11T15:49:06Z")
Links to Github sources on this page are incorrect: [Architecture Deep Dive - FoundationDB Documentation](https://foundationdb.vercel.app/7.3/guides/architecture-deep-dive/) [https://github.com/apple/foundationdb/blob/main/fdbserver/Coordination.actor.cpp](https://github.com/apple/foundationdb/blob/main/fdbserver/Coordination.actor.cpp) [https://github.com/apple/foundationdb/blob/main/fdbserver/ClusterController.actor.cpp](https://github.com/apple/foundationdb/blob/main/fdbserver/ClusterController.actor.cpp) [https://github.com/apple/foundationdb/blob/main/fdbserver/TLogServer.actor.cpp](https://github.com/apple/foundationdb/blob/main/fdbserver/TLogServer.actor.cpp) Files no longer exist. ---
**Author:** ![panghy](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/panghy/32/19_2.png) [@panghy](https://forums.foundationdb.org/u/panghy)\ **Post date:** [May 12, 2026, 5:00am UTC](https://forums.foundationdb.org/t/doc-site-updates-may-2026/5241/6 "2026-05-12T05:00:45Z")
Thank you! > > > \*\*Summary:\*\* Updates three GitHub source code links in the Architecture Deep Div…e documentation that pointed to non-existent file paths. These files were refactored into subdirectories in the FoundationDB repository. > > \*\*Changes:\*\* > \- Fix Coordinators section link from \`fdbserver/Coordination.actor.cpp\` to \`fdbserver/coordinator/Coordination.cpp\` > \- Fix Cluster Controller section link from \`fdbserver/ClusterController.actor.cpp\` to \`fdbserver/clustercontroller/ClusterController.actor.cpp\` > \- Fix Transaction Logs section link from \`fdbserver/TLogServer.actor.cpp\` to \`fdbserver/tlog/TLogServer.cpp\` > > \*\*Files Modified:\*\* > \- \`docs/guides/architecture-deep-dive.md\` > > \*\*Testing:\*\* Links have been verified against the current FoundationDB repository structure and now point to valid source files. > > \--- > Pull Request opened by \[Augment Code\](https://www.augmentcode.com/) with guidance from the PR author ---
**Author:** ![RossWilliams](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/rosswilliams/32/1996_2.png) [@RossWilliams](https://forums.foundationdb.org/u/RossWilliams)\ **Post date:** [May 15, 2026, 11:05am UTC](https://forums.foundationdb.org/t/doc-site-updates-may-2026/5241/7 "2026-05-15T11:05:07Z")
Old doc site still says cluster files must use ip addresses, but hostname support was added in 7.0 or 7.1. [Administration — FoundationDB ON documentation](https://apple.github.io/foundationdb/administration.html) says “The cluster file contains a connection string consisting of a cluster identifier and a comma-separated list of IP addresses (not hostnames) specifying the coordination servers” and [FoundationDB Architecture — FoundationDB ON documentation](https://apple.github.io/foundationdb/kv-architecture.html) says “with a cluster file, which contains the IP:PORT of the coordinators”. ---
**Author:** ![panghy](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/panghy/32/19_2.png) [@panghy](https://forums.foundationdb.org/u/panghy)\ **Post date:** [May 15, 2026, 12:28pm UTC](https://forums.foundationdb.org/t/doc-site-updates-may-2026/5241/8 "2026-05-15T12:28:58Z")
The old doc site is only marginally maintained right now since the new doc site is a WIP to replace that (moving from sphinx to mkdocs).