The ScyllaDB team announces the release of ScyllaDB Enterprise 2019.1.5, a production-ready ScyllaDB Enterprise patch release. As always, ScyllaDB Enterprise customers are encouraged to upgrade to ScyllaDB Enterprise 2019.1.5 in coordination with the ScyllaDB support team.
The focus of ScyllaDB Enterprise 2019.1.5 is improving stability, robustness, reducing memory footprint and bug fixes. The most urgent fix is for users using both Hinted Handoff and Counters. More below.
- Get ScyllaDB 2019.1.5 (customers only, or 30-day evaluation)
- Upgrade from 2019.1.x to 2019.1.5
- Upgrade from 2018.1.x to 2019.1
- Upgrade from ScyllaDB Open Source 3.0 to ScyllaDB 2019.1
- Submit a ticket
Fixed issues in this release are listed below, with open source references, if present:
- Correctness: Hinted handoff (HH) sends counter hints as counter updates when a node targeted by the hint does not exist. This may cause wrong counter value when HH is enabled, Counters are used, and nodes are down. #5833 #4505
- Correctness: wrong encoding of a negative value of type varint. More details in #5656
- Correctness: Materialized Views: virtual columns in a schema may not be propagated correctly #4339
- CQL: error formats field name as a hex string instead of text #4841
- Stability: Running nodetool clearsnapshot can cause a failure, if a new snapshot is created at the exact same time #4554 #4557
- Stability: using an invalid time UUID can cause ScyllaDB to exit. For example
select toDate(max(mintimeuuid(writetime(COLUMN))))” #5552
- Stability: out of memory in cartesian product IN queries, where each column filter is multiple by all other filters. For example:
create table tab ( pk1 int, pk2 int, pk3 int, pk4 int, pk5 int, pk6 int, pk7 int, pk8 int, pk9 int, primary key((pk1, pk2, pk3, pk4, pk5, pk6, pk7, pk8, pk9)) ); select * from tab where pk1 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) and pk2 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) and pk3 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) and pk4 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) and pk5 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) and pk6 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) and pk7 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) and pk8 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10) and pk9 in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10); ServerError: std::bad_alloc
- Stability: IPv6 – seed nodes do not connect to peers with the scope field #5225
- Stability: a graceful shutdown fais produce an error when Tracing is on
[with Service = tracing::tracing]: Assertion `local_is_initialized()'#5243
- Stability: running a misformatted ALTER command on a UDT will cause a crash #4837
- Stability: Replace dead node for a seed is allowed but does not work #3889
- Stability: Immediate abort on OS errors EBADF (Bad file number) and ENOTSOCK (Socket operation on non-socket). These errors usually hint on a deeper root cause, and aborting as soon as possible is both safer and makes it easier to analyze.
- Stability: downgrade assert on
row: append(): downgradeto an error. The assertion, introduced in 2019.1.4 proved to be too strict, aborting on cases which are not fatal.
- Stability: storage_proxy: limit resources consumed in cross-shard operations
Performance: New configuration option,
enable_shard_aware_drivers, allows disabling shard aware drivers from the server (ScyllaDB) side
- Reduce memory footprint: ScyllaDB keeps SSTable metadata in memory #4915
- Reduce memory footprint: cell locking data structures consume 64KiB of RAM per table #4441
- Install: ScyllaDB installs wrong java version on Ubuntu 18.04 #4548
26 Feb 2020