The ScyllaDB team is pleased to announce the release of ScyllaDB 1.7.2, a bugfix release of the ScyllaDB 1.7 stable branch.
Release 1.7.2, like all past and future 1.x.y releases, is backward compatible and supports rolling upgrades. If you are upgrading from 1.6.x to 1.7.2, make sure to read ScyllaDB 1.7 release notes first. In particular, some of the metric names have changed.
Related links
- Get started with ScyllaDB 1.7.2
- Upgrade from 1.6.x to 1.7.y
- Upgrade from 1.7.x to 1.7.2
- Please let us know if you encounter any problems.
The following bugs were fixed in this ScyllaDB release:
- ScyllaDB fails to properly close Thrift connections, which may cause ScyllaDB to exit with “Assertion `!_in_batch’ failed” message #499, #2437
- scylla_setup: posix_net_conf.sh script may fail when bonding iface configuration #2269
- scylla_setup: scylla_setup gets stuck when executes with invalid options #2305
- Repair: significantly improve repair performance by iterating over subranges without building a list of them in advance #2430
- Using User Defined Type (UDT) may cause a minor memory leak #2468
- Dropping a keyspace with nested UDT results in a “Cannot drop user type” error #2490
- Truncating the same table twice in a row might cause ScyllaDB to crash #2489
- Large RPC messages can block the RPC server, and as a result, cause out of memory exception #2453
- Accessing already freed memory may cause ScyllaDB to return wrong results on rare events #2482
- Nodetool: nodetool cleanup may cause segfaults #2537
- ScyllaDB tools: sstabledump throws exception when extracting a user-defined data type scylla-tools #27
- node_exporter, the OS level metric report agent, reports an error when reporting disk usage metrics #2097
