The ScyllaDB team announces ScyllaDB Enterprise 2020.1.9, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2020.1. Note that the latest stable version of ScyllaDB Enterprise is 2021.1 and users are encouraged to upgrade to it.
As always, ScyllaDB Enterprise customers are encouraged to upgrade in coordination with the ScyllaDB support team.
List of stability improvements and bug fixes below.
Related Links
- Get ScyllaDB 2020.1.9 (customers only, or 30-day evaluation)
- Upgrade from 2019.1.x to 2020.1
- Upgrade from 2019.1.x to 2019.1.y
- Upgrade from ScyllaDB Open Source 4.0 to ScyllaDB 2020.1
- Submit a ticket
Fixed issues in this release are listed below, with open source references, if present:
- When aggregating (for example,
SELECT count(*) FROM tab), ScyllaDB internally fetches pages until it is able to compute a result (in this case, it will need to read the entire table). Previously, each page fetch had its own timeout, starting from the moment the page fetch was initiated. As a result, queries continued to be processed long after the client gave up on them, wasting CPU and I/O bandwidth. This was changed to have a single timeout for all internal page fetches for an aggregation query, limiting the amount of time it can be alive. #1175 - Stability: Reject replacing a node that has left the ring #8419
- Rolling upgrade from 2019.1 to 2020.1 failed with error similar to:
[shard 0] gossip - Fail to apply application_state: std::runtime_error (endpoint_state_map does not contain endpoint = x.x.x.x, application_states = [{SCHEMA, Value(e19491c4-2b9b-1111-aaaa-1da25514d39b,36)}] - Stability: a race condition can cause coredump in truncating a table after refresh #7732
- Stability: Reject replacing a node that has left the ring #8419
- Stability: Exceptions in resharding and reshaping are being incorrectly swallowed #8657
23 Jun 2021
