See all blog posts

ScyllaDB Manager Releases 2.0.2 and 1.4.4

ScyllaDB Manager Release Note

ScyllaDB Manager Release 2.0.2

ScyllaDB Manager is a management system that automates maintenance tasks on a ScyllaDB cluster.
Release 2.0.2 is a bug fix release of the ScyllaDB Manager 2.0 branch.

ScyllaDB Enterprise customers are encouraged to upgrade to ScyllaDB Manager 2.0.2 in coordination with the ScyllaDB support team.

Useful Links:

Bugs fixed and improvement in this release

  • Backup:
    • Fix for a memory leak in AWS SDK making ScyllaDB Manager Agent consume huge amounts of memory when uploading data to S3.
    • New scyllamgr_agent_setup script that helps to set up a cgroup for ScyllaDB Manager Agent to run in.
    • Improvements to S3 upload resilience and stability.
    • Improvements to backups files listing containing very large amounts of files.
  • Repair:
    • Relevant for Open-Source ScyllaDB versions 3.1+, adjustments to ScyllaDB Row Level Repair. For the relevant versions ScyllaDB Manager would not split tokens to shards.

ScyllaDB Manager Release 1.4.4

The ScyllaDB team is also pleased to announce the release of ScyllaDB Manager 1.4.4.

ScyllaDB Manager is a management system that automates maintenance tasks on a ScyllaDB cluster. Release 1.4.4 is a bug fix release of the ScyllaDB Manager 1.4 release.

Please note that the latest ScyllaDB Manager Stable branch is Manager 2.0.x, and it is recommended to upgrade to it.

Related Links

Bugs fixed and improvement in this release

  • Skip repairing keyspaces having no replicas in given DC. Repair task fails when repair is being run on DC where kespace doesn’t have any replicas. This change allows skipping such keyspace and repairing all the rest keyspaces.
  • Improvements to ssh communication reliability allow Manager to apply retries after a connection reset.

About Tzach Livyatan

Tzach Livyatan has a B.A. and MSc in Computer Science (Technion, Summa Cum Laude), and has had a 15 year career in development, system engineering and product management. In the past he worked in the Telecom domain, focusing on carrier grade systems, signalling, policy and charging applications.