Skip to content

Release 7.4.9

Pre-release
Pre-release

Choose a tag to compare

@foundationdb-ci foundationdb-ci released this 13 Nov 00:46
· 5 commits to release-7.4 since this release
7.4.9
b94aee2

AVX enabled release.

  • 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 #14334), (PR #14433)
  • On rhel9 based distros, avoid linking GLIBC_2.35 symbols. This fixes compatibility with RHEL 9.6 (and equivalent), and other linux distributions with glibc-2.34 (which lack some symbol backports added in RHEL 9.7). This issue affected FoundationDB 7.4.7 and 7.4.8. (PR #14274)
  • Fixed a client crash (SIGSEGV) when opening a tenant on a database whose cluster file could not be used (missing, or not a valid connection string). Operations on the tenant now fail with the database's error instead. (PR #14308)
  • Fixed clients hanging, with every transaction timing out (error 1031) under the multi-version client, when the connection string still listed a coordinator hostname that no longer resolves in DNS. The client's protocol version check kept retrying that hostname instead of following the switch to a working coordinator. (PR #14338)
  • Fixed global configuration permanently missing the latest committed update after a protocol upgrade, when a refresh accepted an older cached GRV proxy snapshot. (PR #14363)
  • Fixed data distribution picking its primary DC from the highest-priority configured region instead of the active master's DC, which after a region failover made it treat the old primary region as active. (PR #14387)
  • Fixed a memory leak in fdbmonitor on Linux each time a watched configuration file symlink is re-resolved. (PR #14379)
  • Fixed can_clean_bounce always being false in status json. (PR #14272)
  • Fixed storage server finished_queries drifting below total_queries when a read was cancelled or failed, which made query_queue_max in status json grow permanently. (PR #13908)
  • 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 an error field. (PR #14491)
  • 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_PRIORITY client knob default from 1 to 2. Backup agents older than 7.4.9 only run tasks up to priority 1, so keep at least one 7.4.9 or newer backup agent running for backups that ran under 7.4.9. (PR #14390)
  • Added per-URL blobstore parameters for backups: server_side_encryption (or sse) overrides the BLOBSTORE_ENCRYPTION_TYPE knob (sse=none sends no server-side encryption header), proxy overrides the --proxy option and proxy environment variables (proxy=none connects directly), and aws_v4_header (or v4) overrides the HTTP_REQUEST_AWS_V4_HEADER knob. The URL is saved with the backup, so each backup on a cluster can use its own values. (PR #14420), (PR #14471)
  • fdbbackup status now shows the backup's mutation log type (default or partitioned-log-experimental). The same value is in fdbbackup status --json (MutationLogType), in status json on each backup tag under layers.backup (mutation_log_type), and in fdbrestore status (Mutation Log Type:). (PR #14335)
  • Added a bounded-time rollback for shard-encoded location metadata (SHARD_ENCODE_LOCATION_METADATA). New configure options shard_metadata_format={original|encoded} and shard_metadata_migration={enabled|disabled} (default disabled) let data distribution actively rewrite shard-encoded metadata back to the original format when it starts, so the binary can be downgraded (moving to encoded still happens through normal data moves), and audit_storage metadata_encoding in fdbcli reports the encoding state of the cluster. Nothing changes until an operator sets these options. (PR #13965)
  • 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_REGION knob is set and the cluster has more than one usable region. Previously the target was decided by the lexicographic order of DC ids. (PR #14276), (PR #14385)
  • Added opt-in audit logging to fdbcli. With --audit-log (or FDB_CLI_AUDIT_LOG_ENABLE), every key returned by get, getrange, getrangekeys and getall is logged as an FdbCliAudit trace event. --audit-log-values (none, system or all, default system) picks which values are logged. Audit events go to their own trace_audit.* files, in the FDB_CLI_AUDIT_LOG_ENABLE value or --audit-log-dir if set, else next to the trace files, else the current directory. (PR #14485)
  • Added opt-in JSON audit logging to transaction_profiling_analyzer.py. With --audit-log (or FDB_TRANSACTION_PROFILER_AUDIT_LOG_ENABLE), every key, range and mutation it prints is appended to transaction_profiling_analyzer_audit.json, in the FDB_TRANSACTION_PROFILER_AUDIT_LOG_ENABLE value or --audit-log-dir if set, else the FDB_NETWORK_OPTION_TRACE_ENABLE directory, else the current directory. (PR #14485)

This release is compiled with avx instructions enabled.

Full release notes: 7.4 release notes

All changes: 7.4.8...7.4.9