Release Notes

4.6.5

Bindings

4.6.4

Features

  • Added ability to use –io_trust_seconds in a warn-only mode, which logs a trace event rather than failing the process when a disk operation takes a long time. This is enabled with –io_trust_warn_only. <rdar://problem/32344389>

Fixes

  • Disk operation timeouts now cause the process to restart rather than hang indefinitely. <rdar://problem/31888796>
  • fdbdr switch did not start the DR in the opposite direction correctly, resulting in mutations being lost. <rdar://problem/32598128>
  • Lowered backup and DR batch sizes to avoid large packet warnings. <rdar://problem/30933203>
  • Remove partial pipelining of tlog commits.

4.6.3

Features

Fixes

  • Added the ability to automatically shutdown processes if a disk operation takes a long time to complete. This is enabled with –io_trust_seconds. <rdar://problem/31229332>
  • Too many outstanding storage recruitment requests causes the cluster controller to hang. <rdar://problem/30271581>
  • Corrected issue with Ubuntu installer package on Ubuntu 16.04 not starting daemon. <rdar://problem/27752324>
  • Package non-Linux builds of JNI component into Java jars. <rdar://problem/30786246>
  • Published backup-related binaries on macOS were incorrectly pointing to symbolic link specification files. <rdar://problem/31403408>

Performance

4.6.2

Fixes

Performance

  • Storage engine performance improvements to reduce the overhead that ssd-2 requires for its benefits over ssd-1 <rdar://problem/29332661>
  • Lowered the default fetch keys parallelism to slow down data distribution <rdar://problem/29934862>

4.6.1

Fixes

4.6.0

Features

Performance

Fixes

Bindings

  • API version updated to 460. There are no behavior changes in this API version. See the API version upgrade guide for upgrade details.

Status

  • The following fields were added: cluster.data.moving_data.total_written_bytes, cluster.qos.limiting_queue_bytes_storage_server, cluster.qos.worst_version_lag_storage_server, cluster.qos.limiting_version_lag_storage_server, cluster.qos.transaction_per_second_limit, cluster.qos.released_transactions_per_second, cluster.qos.performance_limited_by.reason_id, and cluster.database_available