FoundationDB
Publicly indicated next
- prereleaseRelease 7.3.79Published 2026-07-15
- prereleaseRelease 7.3.78Published 2026-07-15
Prereleases and milestones indicate public plans; they are not delivery commitments.
18 signals · 20 observation events
FoundationDB - the open source, distributed, transactional key-value store
Prereleases and milestones indicate public plans; they are not delivery commitments.
## Summary - Preserve the first observed maintenance-window start version when a transaction must be retried. - Adopt an already committed start after ambiguous commits, concurrent writers, or data-distributor recruitment. - Retry stale-start cleanup when maintenance ends while preserving the existing maintenance tracing and durable storage format. - Cover f
## Summary - Pause CDC stream initialization after its durable metadata read using existing simulation-only pop controls. - Synchronize the existing test-only status endpoint with pending stream initialization without changing CDC interfaces or serialized state. - Remove a paused stream in the assignment-publication workload, verify the outstanding consume f
## Summary - Reject acknowledgements and removals sent to a non-owning CDC proxy. - Ensure removal retried with an obsolete stream ID cannot delete its same-name replacement. - Promote all three deterministically covered ownership probes from rare to required coverage. ## Testing - `fdbclient_test`: 90/90 passed. - `fdbserver_cdcproxy_test`: 11/11 passed. -
also update supported OS version guidance (will validate by building docs locally and testing the links) After this, I can backport all docs-site updates to release-7.4 branch for inclusion in the next 7.4.x release. We could consider updating these version numbers just _before_ building the release, to match the impending release, but we do not mark a relea
## Summary - Extract native CDC stream and tag routing into a dedicated `CDCRoutingTable` log-system module. - Keep metadata mutation application focused on durable metadata updates while making the commit proxy's routing dependency explicit. - Preserve stream metadata ordering, tag-version rotation, overlapping ranges, and shared-tag routing. - Add focused
## Summary - Convert load-balancing, replica-comparison, and TSS-comparison actors to standard C++ coroutines. - Consolidate the migrated implementation into `fdbrpc/LoadBalance.h` and update direct includes so the header no longer requires actor compilation. - Preserve request ownership, cancellation, inert `Never()` handling, race ordering, replica consist
Bumps the pip group with 1 update in the /documentation/sphinx directory: [setuptools](https://github.com/pypa/setuptools). Updates `setuptools` from 78.1.1 to 83.0.0 <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pypa/setuptools/blob/main/NEWS.rst">setuptools's changelog</a>.</em></p> <blockquote> <h1>v83.0.0</h1> <h2
I think setuptools really isn't needed here, I think it was added for an older version of python and pip. I'm not sure it really worked in this spot anyway: it's possible that someone may have had to install or update setuptools before pip could install some source package requirements here, but that would have to happen before the pip install of these requi
### Result of foundationdb-pr-cluster-tests on Linux RHEL 9 * Commit ID: 2c9d0df92aad201171ba3d025e87e216aee7a66a * Duration 1:29:03 * Result: :white_check_mark: **SUCCEEDED** * Error: `N/A` * [Build Log](https://d1e0l78xbkh3xa.cloudfront.net/foundationdb/foundationdb-pr-cluster-tests/7590ad32-3ea2-4cd4-9352-d221b57f7f08.gz) terminal output (available for 30
RockyLinux 10 adds new architecture riscv64, a per-requisite for building riscv64 releases. * Update the base image to RockyLinux 10.1 # Code-Reviewer Section The general pull request guidelines can be found [here](https://github.com/apple/foundationdb/wiki/FoundationDB-Commit-Process). Please check each of the following things and check *all* boxes before a
## Summary A partitioned backup can finish after recovery has selected backup workers for an older transaction-log generation but before those workers read the backup-start key. When the last active backup clears that key, the old-generation workers wait for a future backup instead of acknowledging completion. Their obsolete transaction-log generation remain
This backports [#10791](https://github.com/apple/foundationdb/pull/10791) ([`22ddb8a92`](https://github.com/apple/foundationdb/commit/22ddb8a92d473aafb18f15c436bb8cce17e562ee)) to `release-7.3`. The async status backport in #13068 can still let coordinator DNS, blob-granule, or blob-restore sub-fetcher timeouts escape the status actor. That aborts status col
Append Major.Minor to titles of release-notes pages so they better distinguish themselves. URLs do not change, they are based on filename. Consolidate pre-1.0 alpha and beta release notes into the 1.0 page (subjective 🤷) Latest release-notes-740 keep version-less title because of links to "latest Release Notes" elsewhere in the docs site that would be affect
Added functionality for `fdb.bash` to support ipv6, provided the new env variable `FDB_IP_VERSION` is set to 6 (or any string containing 6, such as v6, ipv6, iwantipv6, etc. ) There is an unfortunate caveat of no dual stack support, as FDB coordinators are recognized by their IP+port and not their machineid, to the best of my knowledge. If I'm wrong and FDB