Release Notes

5.2.8

Java: FDBDatabase::run and FDBDatabase::read now use the Executor provided for executing asynchronous callbacks instead of the default one for the database. (Issue #640)

A large number of concurrent read attempts could bring the database down after a cluster reboot. (PR #650)

The go bindings now caches database connections on a per-cluster basis. (Issue #607)

A client could fail to connect to a cluster when the cluster was upgraded to a version compatible with the client. This affected upgrades that were using the multi-version client to maintain compatibility with both versions of the cluster. (PR #637)
Incorrect accounting of incompatible connections led to occasional assertion failures. (PR #637)

Improved backup error specificity regarding timeouts and active connection failures. (PR #581)

A memory leak was fixed in connection closing. (PR #574)
A memory leak was fixed in the coordinator’s handling of disconnected clients. (PR #579)
Aligned memory allocation on MacOS was sometimes failing to allocate memory, causing a crash. (PR #547)

Backup and DR share a single mutation log when both are being used on the same cluster. Ongoing backups will be aborted when upgrading to 5.2. (PR #3)
Added a TLS plugin implementation. (PR #343)
Backup supports HTTPS for blobstore connections. (PR #343)
Added the APPEND_IF_FITS atomic operation. (PR #22)
Updated the SET_VERSIONSTAMPED_KEY atomic operation to take four bytes to specify the offset instead of two (if the API version is set to 520 or higher). (Issue #148)
Updated the SET_VERSIONSTAMPED_VALUE atomic operation to place the versionstamp at a specified offset in a value (if the API version is set to 520 or higher). (Issue #148)
tls_verify_peers splits input using the ‘|’ character. [5.2.4] (PR #468)
Added knobs and blob Backup URL parameters for operations/sec limits by operation type. [5.2.5] (PR #513)

The client did not clear the storage server interface cache on endpoint failure for all request types. This causes up to one second of additional latency on the first get range request to a rebooted storage server. (Issue #351)
Client input validation would handle inputs to versionstamp mutations incorrectly if the API version was less than 520. [5.2.1] (Issue #387)
Build would fail on recent versions of Clang. [5.2.2] (PR #389)
Clusters running with TLS plugin would reject clients using non-server certificates. [5.2.2] (PR #396)
Backup would attempt to clear too many ranges in a single transaction when erasing log ranges. [5.2.3] (PR #440)
A read-only transaction using the READ_LOCK_AWARE option would fail if committed. [5.2.3] (PR #437)
fdbcli kill command did not work when TLS was enabled. [5.2.4] (PR #471)
Don’t disable certificate checks by default. [5.2.5] (PR #511)

Available space metrics for the memory storage engine take into account both memory and disk. (PR #41)
Added metrics for read bytes per second and read keys per second. (PR #303)

API version updated to 520. See the API version upgrade guide for upgrade details.
Java and Python: Versionstamp packing methods within tuple class now add four bytes for the offset instead of two if the API version is set to 520 or higher. (Issue #148)
Added convenience methods to determine if an API version has been set. (PR #72)
Go: Reduce memory allocations when packing tuples. (PR #278)
Python: Correctly thread the versionstamp offset when there are incomplete versionstamps within nested tuples. (Issue #356)
Java: Length in Tuple.fromBytes is now honored if specified. (Issue #362)

Deprecated the read_ahead_disable option. The commit_on_first_proxy, debug_dump, and check_writes_enable options are no longer exposed through the bindings. (PR #134)