Released on 2021-08-19.
- Release v. 1.10.11.
1.10.11 is the next stable release in the long-term support (LTS) version 1.10.x release series.
The label “stable” means there are 1.10.x-based applications running in production for quite a while without known crashes, incorrect results or other showstopper bugs.
This release introduces 2 improvements and resolves roughly 18 issues since version 1.10.10.
Tarantool 1.10.x is backward compatible with Tarantool 1.9.x in binary data layout, client-server protocol and replication protocol.
box.schema.upgrade() procedure to unlock all the new
features of the 1.10.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.
- Introduced support for
- 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
Fixed invalid results of the
encodefunction when it was used from the Lua garbage collector. For example, this could happen in functions used as
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).
Fixed a bug when iterators became invalid (up to crash) after schema change (gh-6147).
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 possible keys divergence during secondary index build, which might lead to missing tuples (gh-6045).
- Fix crash which may occur while switching read_only mode due to duplicating transaction in tx writer list (gh-5934).
- Fixed the race between Vinyl garbage collection and compaction that resulted in a broken vylog and recovery failure (gh-5436).
- Fixed replication occasionally stopping with
ER_INVALID_MSGPACKwhen the replica is under high load (gh-4040).
- 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).