Released on 2021-08-19.
- Release v. 2.7.3.
2.7.3 is the second stable version of the 2.7 release series. It introduces 6 improvements and resolves 49 bugs since version 2.7.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.
box.schema.upgrade() procedure to unlock all the new
features of the 2.x series.
Some changes are labeled as [Breaking change]. It means that the old behavior was considered error-prone and therefore changed to protect users from unintended mistakes. However, there is a small probability that someone can rely on the old behavior, and this label is to bring attention to the things that have been changed.
- The information about the state of synchronous replication is now available via the
- Introduced support for
- Introduced the new method
table.equals. It compares two tables by value with respect to the
Descriptions of type mismatch error and inconsistent type error have become more informative (gh-6176).
Removed explicit cast from
BOOLEANto numeric types and vice versa (gh-4770).
CAST(FALSE AS INTEGER)was
0in version 2.8. Now it causes an error.
Removed explicit cast from
VARBINARYto numeric types and vice versa (gh-4772, gh-5852).
Fixed a bug where a string that is not
NULL-terminated could not be cast to
BOOLEAN, even if the conversion would be successful according to the rules.
- Fedora 34 builds are now supported (gh-6074).
- Fedora 28 and 29 builds are no longer supported.
fiber.wakeup()in Lua and
fiber_wakeup()in C became NOP on the currently running fiber. Previously they allowed “ignoring” the next yield or sleep, which resulted in unexpected erroneous wake-ups. Calling these functions right before
fiber.create()in Lua or
fiber_start()in C could lead to a crash (in debug build) or undefined behaviour (in release build) (gh-6043).
There was a single use case for the previous behaviour: rescheduling in the same event loop iteration, which is not the same as
fiber.sleep(0)in Lua and
fiber_sleep(0)in C. It could be done in the following way:
and in Lua:
To get the same effect in C, one can now use
fiber_reschedule(). In Lua, it is now impossible to reschedule the current fiber directly in the same event loop iteration. One can reschedule self through a second fiber, but it is strongly discouraged:
-- do not use this code local self = fiber.self() fiber.new(function() self:wakeup() end) fiber.sleep(0)
Fixed memory leak on
fiber_join()now checks if the argument is a joinable fiber. The absence of this check could lead to unpredictable results. Note that the change affects the C level only; in the Lua interface,
fiber:join()protection is already enabled.
Now Tarantool yields when it scans
.xlogfiles for the latest applied vclock and finds the right place to start recovering from. It means that the instance becomes responsive right after the
box.cfgcall even if an empty
.xlogwas not created on the previous exit.
This fix also prevents the relay from timing out when a freshly subscribed replica needs rows from the end of a relatively long (hundreds of MBs)
The counter in
N rows processedlog messages no longer resets on each newly recovered
Fixed invalid results of the
encodefunction when it was used from the Lua garbage collector. For example, this could happen in functions used as
Simultaneously updating a key in different transactions does not longer result in a MVCC crash (gh-6131).
Fixed a bug where memtx MVCC crashed during reading uncommitted DDL (gh-5515).
Fixed a bug where memtx MVCC crashed if an index was created in the transaction thread (gh-6137).
Fixed a MVCC segmentation fault that arose when updating the entire space concurrently (gh-5892).
Fixed crash in case of reloading a compiled module when the new module lacks some functions present in the former code. In turn, this event triggers a fallback procedure where we restore old functions, but instead of restoring each function, we process a sole entry only, leading to the crash later when these restored functions are called (gh-5968).
Fixed a bug with failed assertion after a stress update of the same key (gh-6193).
Fixed a crash where
box.snapshotcould be called during an incomplete transaction (gh-6229).
Fixed console client connection failure in case of request timeout (gh-6249).
Added a missing broadcast to
net.box.future:discard()so that now fibers waiting for a request result wake up when the request is discarded (gh-6250).
tostring(decimal)with any decimal number in Lua could sometimes return garbage if there were
__gchandlers in the user’s code (gh-6259).
Fixed an error message that appeared in a particular case during MVCC operation (gh-6247).
Fixed a repeatable read violation after delete (:gh-6206).
Fixed a bug where the MVCC engine didn’t track the
Fixed a crash in MVCC after a drop of space with several indexes (gh-6274).
Fixed a bug where the GC could leave tuples in secondary indexes (gh-6234).
Disallow yields after DDL operations in MVCC mode. It fixes a crash that took place when several transactions referred to system spaces (gh-5998).
Fixed a bug in MVCC that happened on rollback after a DDL operation (gh-5998).
Fixed a bug where rollback resulted in unserializable behavior (gh-6325).
- Fixed the use after free in the relay thread when using elections (gh-6031).
- Fixed a possible crash when a synchronous transaction was followed by an asynchronous transaction right when its confirmation was being written (gh-6057).
- Fixed an error where a replica, while attempting to subscribe to a foreign
cluster with a different replicaset UUID, didn’t notice it is impossible
and instead became stuck in an infinite retry loop printing
- Fixed an error where a replica, while attempting to join a cluster with exclusively read-only replicas available, just booted its own replicaset, instead of failing or retrying. Now it fails with an error about the other nodes being read-only so they can’t register the new replica (gh-5613).
- Fixed error reporting associated with transactions
received from remote instances via replication.
Any error raised while such a transaction was being applied was always reported as
Failed to write to diskregardless of what really happened. Now the correct error is shown. For example,
Out of memory, or
Transaction has been aborted by conflict, and so on (gh-6027).
- Fixed replication occasionally stopping with
ER_INVALID_MSGPACKwhen the replica is under high load (gh-4040).
- Fixed a cluster sometimes being unable to bootstrap if it contains
- Fixed a possible crash when
box.ctl.promote()was called in a cluster with more than three instances. The crash happened in the debug build. In the release build, it could lead to undefined behaviour. It was likely to happen if a new node was added shortly before the promotion (gh-5430).
- Fixed a rare error appearing when MVCC
box.cfg.memtx_use_mvcc_engine) was enabled and more than one replica joined the cluster. The join could fail with the error
"ER_TUPLE_FOUND: Duplicate key exists in unique index 'primary' in space '_cluster'". The same could happen at the bootstrap of a cluster having more than three nodes (gh-5601).
- Fixed a rare crash with leader election enabled (any mode except
off), which could happen if a leader resigned from its role while another node was writing something elections-related to WAL. The crash was in the debug build, and in the release build it would lead to undefined behaviour (gh-6129).
- Fixed an error where a new replica in a Raft cluster tried to join
from a follower instead of a leader and failed with the error
- Fixed optimization for single-char strings in the
- Fixed slots alignment in the
lj-stackcommand output when
LJ_GC64is enabled (gh-5876).
- Fixed dummy frame unwinding in the
- Fixed detection of inconsistent renames even in the presence of sunk values (gh-4252, gh-5049, gh-5118).
- Fixed the VM register allocation order provided by LuaJIT frontend in case
- When an error occurs during encoding call results, the auxiliary lightuserdata value is not removed from the main Lua coroutine stack. Before the fix, it led to undefined behaviour during the next usage of this Lua coroutine (gh-4617).
- Fixed a Lua C API misuse when the error is raised during call results encoding in an unprotected coroutine and expected to be caught in a different, protected coroutine (gh-6248).
- Fixed a possible crash in case trigger removes itself. Fixed a possible crash in case someone destroys a trigger when it yields (gh-6266).
- User-defined functions can now return a VARBINARY result to SQL (gh-6024).
- Fixed assert when a DOUBLE value greater than -1.0 and less than 0.0 is cast to INTEGER and UNSIGNED (gh-6225).
- Removed spontaneous conversion from INTEGER to DOUBLE in a field of the NUMBER type (:gh-5335).
- All arithmetic operations can now accept numeric values only (gh-5756).