Repository navigation
Release 8.0.1
Pre-release
Pre-release
·
4 commits
to release-8.0
since this release
AVX enabled release.
- Raised the protocol versions that 8.0 binaries treat as the next release from 8.1 to 9.0 (future protocol version 9.0, minimum invalid protocol version 9.1). 8.0.0 rejects data stamped with protocol 8.2 or later, so a future 9.0 cluster can be downgraded only to 8.0.1 or later 8.0.x releases, not to 8.0.0. The current protocol version, minimum compatible version and API version are unchanged. (PR #14423)
- Rejected file and object names that are absolute or contain a
..component in places where a name is joined onto a base directory: local directory backup containers, backup file listing, S3 copy-down, bulk load job and task manifests, the profiler output file, and SST file names in fetched checkpoints. (PR #14421) - Avoided linking newer glibc symbols into RHEL 9 builds that prevented binaries built on RHEL 9.7 from starting on RHEL 9.6 systems and containers. (PR #14278)
- Fixed network setup failures when older multiversion clients load the 8.0 client, even when the application does not use blob granules. Restored the required blob granule C symbols as stubs that abort the process when called. (PR #14239)
- Removed the unused blob granule types
FDBBGMutationTypeand theFDBBG*file description structs fromfdb_c.h. They were only used by the blob granule read API removed in 8.0.0.FDBGranuleSummaryandFDBReadBlobGranuleContextare kept for the compatibility stubs. (PR #14247) - Outbound TLS connections that fdbserver opens by hostname (S3 and other HTTPS blob stores, REST and KMS servers, including connections through an HTTP proxy) are now verified by CA chain and hostname instead of the cluster's
--tls-verify-peersrules. Previously, on clusters that set peer rules, every S3 server certificate was rejected, which broke bulk dump and bulk load uploads. Cluster traffic keeps using the peer rules. (PR #14469) - Fixed an interrupted remote-region recovery possibly starting the next generation one version too late and leaving a storage server behind, because a new log router reported its synthetic startup pop floor as committed progress. (PR #14295)
- Added the
SS_SKIP_DELIVERED_TO_NOT_ASSIGNED_VERSIONserver knob (default0, disabled) to recover a storage server that crash-loops on a mutation delivered to a shard it is not assigned. Setting it to that one version makes the storage server drop such mutations at that version instead of asserting. (PR #14480) - Fixed DR (
fdbdr) mutation log copying possibly skipping mutations when a copy step timed out. Copying now finishes the current version and resumes at the first version it did not copy. (PR #14296) - Fixed a race in the client library where an application thread could destroy a result while the network thread was still completing it, which could crash the client. (PR #14373)
- Fixed a client memory leak when setting watches on many distinct keys. Watch reference-count entries are now removed once no watch uses them. (PR #14490)
- Retried
fallocate()andftruncate()when they fail withEINTRin the Linux KAIO file truncate path, instead of failing the operation. (PR #14326) - Fixed Redwood page-cache memory accounting when a reused page ID changes size, so cache eviction uses the current page size. (PR #14291)
- Fixed a Linux
fdbmonitormemory leak when changes to a configuration-file symlink caused its target path to be resolved again. (PR #14253) - Remote-region TLogs reuse recent disk-space samples in the low-disk admission check instead of calling
statvfs()for every version they pull. On a two-region cluster under write load, the per-version disk checks made spilling fall behind, and remote TLogs ran out of memory during a machine exclude. (PR #14345) - Reduced CPU spent on every completed RPC reply. Cancelling the per-request failure monitor wait no longer throws C++ exceptions. (PR #14352)
- Cached the network interface name used for network-traffic metrics to reduce periodic network-thread stalls on hosts with many interfaces. (PR #14283)
- Fixed one backup with a missing or invalid container URL dropping every backup from the backup layer status in
status json(layers.backup). The other backups are still reported, and the failing one gets anerrorfield. (PR #14484) - Mutation log tasks of a backup whose snapshot has finished now run ahead of other backups' initial snapshot tasks, so a new backup's first snapshot no longer starves other backups' logs and increases their backup lag. This raises the
TASKBUCKET_MAX_PRIORITYclient knob default from 1 to 2. Backup agents older than 8.0.1 (and older than 7.4.9 on 7.4) only run tasks up to priority 1, so keep at least one 8.0.1 or newer backup agent running for backups that ran under 8.0.1, and do not downgrade all backup agents while a backup is running. (PR #14499) - Added bounded retries for disk errors when opening or reading backup encryption-key files, allowing transient failures to recover before the backup container retains a failed initialization result. (PR #14294)
- Added per-URL blobstore parameters for backups:
server_side_encryption(orsse) overrides theBLOBSTORE_ENCRYPTION_TYPEknob (sse=nonesends no server-side encryption header),proxyoverrides the--proxyoption and proxy environment variables (proxy=noneconnects directly), andaws_v4_header(orv4) overrides theHTTP_REQUEST_AWS_V4_HEADERknob. The URL is saved with the backup, so each backup on a cluster can use its own values. (PR #14519), (PR #14521) - Range file restores now send one clear per restore transaction instead of one clear per gap between restored keys, and skip that clear when the range has no existing keys. In tests on 20-storage-server clusters this made restores about 2x faster and roughly halved storage server CPU. Setting the client knobs
RESTORE_RANGE_DISABLE_RYWorRESTORE_RANGE_READ_BEFORE_CLEAR(both defaulttrue) tofalseon the backup agents restores the previous behavior. (PR #14513), (PR #14525) - Bulk dump now picks its target DC from the region configuration: the primary region by default, or the remote region when the new
DD_BULKDUMP_USE_REMOTE_REGIONknob is set and the cluster has more than one usable region. Previously the target was decided by the lexicographic order of DC ids. (PR #14275), (PR #14384) - Added opt-in audit logging to fdbcli. With
--audit-log(orFDB_CLI_AUDIT_LOG_ENABLE), every key returned byget,getrange,getrangekeysandgetallis logged as anFdbCliAudittrace event.--audit-log-values(none,systemorall, defaultsystem) picks which values are logged. Audit events go to their owntrace_audit.*files, in theFDB_CLI_AUDIT_LOG_ENABLEvalue or--audit-log-dirif set, else next to the trace files, else the current directory. (PR #14486) - Added opt-in JSON audit logging to
transaction_profiling_analyzer.py. With--audit-log(orFDB_TRANSACTION_PROFILER_AUDIT_LOG_ENABLE), every key, range and mutation it prints is appended totransaction_profiling_analyzer_audit.json, in theFDB_TRANSACTION_PROFILER_AUDIT_LOG_ENABLEvalue or--audit-log-dirif set, else theFDB_NETWORK_OPTION_TRACE_ENABLEdirectory, else the current directory. (PR #14486) - Fixed truth testing of an absent value in the Python bindings on Python 3.
if not tr[key]:raisedTypeErrorfor a missing key and now evaluates as false. (PR #14517) - Fixed
FDB::Tuple.compareandFDB::Tuple::SingleFloatcomparisons raisingArgumentErroron Ruby 3.3 and later when comparing floating point values. (PR #14518) - Changed the Kubernetes monitor image to declare its existing non-root user numerically, allowing it to start with
runAsNonRoot: truewhenrunAsUseris not specified. (PR #14248) - Updated
fdb-kubernetes-monitor: it retries loading its configuration while thefdbserverbinary is missing, empty or not executable, can be configured to always use the shared binaries (useful for compatible version upgrades without recreating pods), and exposes the staged and runningfdbserverversions in a pod annotation for the operator. Its Go toolchain and dependencies now matchmain. (PR #14556)
This release is compiled with avx instructions enabled.
Full release notes: 8.0 release notes
All changes: 8.0.0...8.0.1