Tarantool 2.5.3
Release: v. 2.5.3 Date: 2020-12-30 Tag: 2.5.3-0-gf93e480
2.5.3 is the second stable version of the 2.5 release series. It introduces one improvement and resolves 19 bugs since 2.5.2.
The “stable” label means that we have all planned features implemented and we see no high-impact issues. However, if you encounter an issue, feel free to report it on GitHub.
Tarantool 2.x is backward compatible with Tarantool 1.10.x in the binary data layout, client-server protocol, and replication protocol.
Please
upgrade
using the box.schema.upgrade() procedure to unlock all the new
features of the 2.x series.
It is now possible to specify synchro quorum as a function of a number
Nof registered replicas instead of aconstnumber, for example:box.cfg{replication_synchro_quorum = "N/2 + 1"}
Only the non-anonymous bootstrapped replicas amount to
N. The expression should respect synchro guarantees: at least 50% of the cluster size + 1. The expression value is re-evaluated automatically inside of Tarantool when new replicas appear or old ones are removed (gh-5446).
fiber.cond:wait()now correctly throws an error when a fiber is cancelled, instead of ignoring the timeout and returning without any signs of an error (gh-5013).- Fixed a memory corruption issue, which was most visible on macOS, but could affect any system (gh-5312).
- A dynamic module now gets correctly unloaded from memory in case of an attempt to load a non-existing function from it (gh-5475).
- A
swim:quit()call now can’t result in a crash (gh-4570). - Snapshot recovery with no JSONPath or multikey indices involved now has normal performance (gh-4774).
- A false-positive “too long WAL write” message no longer appears for synchronous transactions (gh-5139).
- A
box.ctl.wait_rw()call could return when the instance was not in fact writable due to having foreign synchronous transactions. As a result, there was no proper way to wait until the automatically elected leader would become writable. Nowbox.ctl.wait_rw()works correctly (gh-5440).
- Data changes in read-only mode are now forbidden (gh-5231).
- Query execution now does not occasionally raise an unrelated error “Space ‘0’ does not exist” (gh-5592).
- Coinciding names of temporary files (used to store data during execution) having two instances running on the same machine no longer cause a segfault (gh-5537).
- The return value of
ifnull()built-in function is now of a correct type. - SQL calling Lua functions with box calls inside can no longer result in a memory corruption (gh-5427).
- An attempt to use a
net.boxconnection which is not established yet now results in a correctly reported error (gh-4787). - Fixed a
NULLdereference on error paths in merger which usually happened on a ‘wrong’key_def(gh-5450). - Calling
key_def.compare_with_key()with an invalid key no longer causes a segfault (gh-5307). - Fixed a hang which occured when
tarantoolran a user script with the-eoption and this script exited with an error (like withtarantool -e 'assert(false)') (gh-4983).
- The
on_schema_inittriggers now can’t cause duplicates in primary key (gh-5304). As part of the fix there is a new function, box.ctl.is_recovery_finished().