[RELEASE] ScyllaDB Enterprise 2024.1.13

Release Notes
, ,
1

The ScyllaDB team announces ScyllaDB Enterprise 2024.1.13, a bug-fix production-ready patch release for ScyllaDB Enterprise 2024.1 Long Term Support (LTS) Release.

Note there is a later Feature (Short term Support) Release 2024.2.

Related Links

The following issues are fixed in this release (with an open-source reference, if available):

Performance Related

  • multishard reader: use buffer hint to reduce cross-shard round trips and opportunities for shard reader eviction-recreation cycles. Two new configurations are introduced to support this:
    • Repair_multishard_reader_buffer_hint_size: The buffer size to use for the buffer-hint feature of the multishard reader when running repair in mixed-shard clusters. This can help the performance of mixed-shard repair (including RBNO). Set to 0 to disable the hint feature altogether. Default value: 1024 * 1024
    • Repair_multishard_reader_enable_read_ahead: The multishard reader has a read-ahead feature to improve latencies of range-scans. This feature can be detrimental when the multishard reader is used under repair, as is the case in repair in mixed-shard clusters. This now allows disabling this read-ahead (default), this can help the performance of mixed-shard repair (including RBNO). Default value: false #21113
  • node-exporter: Disable the hwmon temperature collector, as it causes bad performance on Azure. #21163

Stability related

  • tasks: abort method hits use after free #19304

Alternator Related

  • The Alternator /localnodes endpoint will not return nodes that are temporarily down. #21538
  • The Alternator /localnodes REST API returns nodes local to the current datacenter. It is now enhanced to be able to return other datacenters, and to restrict the returned nodes to a specific rack. This can help reduce networking costs. #12147

Upgrade Related

  • Service Level shares did not survive an upgrade from ScyllaDB Open Source 5.4 to Enterprise 2024.1

Tooling and Monitoring

  • Node streaming data to itself can cause deadlock. This might happen when using nodetool refresh --load-and-stream #21570, #21264