Tarantool 2.10.0-beta2

The UUID field type is now part of the SCALAR field type (gh-6042).

The `UUID field type is now available in SQL. A new UUID can be generated using the new SQL built-in function UUID() (gh-5886).

[Breaking change] The timeout() method of the net.box connection, deprecated more than four years ago (in 1.7.4) has been dropped. It negatively affected the performance of hot net.box methods, such as call() and select() if they were called without a specified timeout (gh-6242).

Improved net.box performance by up to 70% by rewriting hot code paths in C (gh-6241).

Introduced compact tuples that allow saving 4 bytes per tuple in case of small userdata (gh-5385).

Now streams and interactive transactions over streams are implemented in iproto. Every stream is associated with its ID, which is unique within one connection. All requests with the same non-zero stream ID belong to the same stream. All requests in the stream are processed synchronously. The next request will not start executing until the previous one is completed. If a request’s stream ID is 0, it does not belong to any stream and is processed in the old way.

In net.box, a stream is an object above the connection that has the same methods but allows executing requests sequentially. The ID is generated on the client side automatically. If a user writes his own connector and wants to use streams, they must transmit the stream_id over the iproto protocol.

The primary purpose of streams is transactions via iproto. As each stream can start a transaction, several transactions can be multiplexed over one connection. There are multiple ways to begin, commit, and rollback a transaction. One can do that using the appropriate stream methods, call, eval, or execute with the SQL transaction syntax. Users can mix these methods. For example, one might start a transaction using stream:begin(), and commit it with stream:call('box.commit') or stream:execute('COMMIT'). If any request fails during the transaction, it will not affect the other requests in the transaction. If a disconnect occurs while there is an active transaction in the stream, that transaction will be rolled back if it hasn’t been committed before the connection failure.

Added the new memtx_allocator option to box.cfg{}. It allows selecting an appropriate allocator for memtx tuples if necessary. Possible values are system for the malloc allocator and small for the default small allocator.

Implemented the system allocator based on malloc. The slab allocator, which is used for tuple allocation, has a particular disadvantage—it is prone to unresolvable fragmentation on specific workloads (size migration). In this case, the user should be able to choose another allocator. The system allocator is based on the malloc function but restricted by the same quota as the slab allocator. The system allocator does not alloc all the memory at the start. Instead, it allocates memory as needed, checking that the quota is not exceeded (gh-5419).

Added box.stat.net.thread() for reporting per thread net statistics (gh-6293).

Add the new metric STREAMS to box.stat.net, which contains statistics for iproto streams. STREAMS contains the same counters as the CONNECTIONS metric in box.stat.net: current, rps, and total (gh-6293).

Extended the network protocol (IPROTO) with a new request type (IPROTO_ID) that is supposed to be used for exchanging sets of supported features between server and client (gh-6253).

Added required_protocol_version and required_protocol_features to net.box connection options. The new options allow to specify the IPROTO protocol version and features that must be supported by the server for the connection to pass (gh-6253).

[Breaking change] Added msgpack.cfg.encode_error_as_ext configuration option to enable/disable encoding errors as MP_ERROR MsgPack extension. The option is enabled by default (gh-6433).

[Breaking change] Removed box.session.setting.error_marshaling_enabled. Error marshaling is now enabled automatically if the connector supports it (gh-6428).

Add new metrics REQUESTS_IN_PROGRESS and REQUESTS_IN_STREAM_QUEUE to box.stat.net, which contain detailed statistics for iproto requests. These metrics contain the same counters as other metrics in box.stat.net: current, rps, and total (gh-6293).

Implemented timeout for fiber:join in Lua (gh-6203).

Updated libev to version 4.33 (gh-4909).

Added the box.txn_id() function. It returns the ID of the current transaction if called within a transaction, nil otherwise.

Previously, if a yield occurred for a transaction that did not support it, Tarantool rolled back all its statements, but still processed its new statements (rolling them back with each yield). Also, the transaction was rolled back when a commit is attempted. Now Tarantool stopped processing any new statements right after the first yield if the transaction does not support it.

Implemented a timeout for transactions after which they are rolled back (gh-6177).

Implemented the new C API function box_txn_set_timeout to set timeout for transaction.

Implemented the new IPROTO_TIMEOUT 0x56 key. It is used to set a timeout for transactions over iproto streams. It is stored in the body of IPROTO_BEGIN request.

Introduced box.broadcast and box.watch functions to signal/watch user-defined state changes (gh-6257).

Added watchers support to the network protocol (gh-6257).

Added watchers support to the net.box connector (gh-6257).

Now error objects with the box.error.READONLY code have the additional fields explaining why the error has happened. Also, there is a new field box.info.ro_reason. It is nil on a writable instance, but reports a reason when the box.info.ro is true (gh-5568).

Implemented ability to open several listening sockets. In addition to ability to pass uri as a number or string, as previously, ability to pass uri as a table of numbers or strings has been added (gh-3554).

[Breaking change] net.box console support, marked deprecated in 1.10, has been dropped. Use require('console').connect() instead.

Added takes_raw_args Lua function option. It wraps the arguments in msgpack.object to skip the decoding (gh-3349).

Introduced support for LJ_DUALNUM mode in luajit-gdb.py (gh-6224).

Introduced preliminary support of GNU/Linux ARM64 and MacOS M1. In the scope of this activity, the following issues have been resolved:

• Introduced support for the full 64-bit range of lightuserdata values (gh-2712).
• Fixed memory remapping issue when the page left 47-bit segments (gh-2712).
• Fixed M1 architecture detection (gh-6065).
• Fixed variadic arguments handling in FFI on M1 (gh-6066).
• Fixed table.move misbehaviour in case of table reallocation (gh-6084).
• Fixed Lua stack inconsistency when xpcall is called on ARM64 with the invalid second argument (gh-6093).
• Fixed BC_USETS bytecode semantics for closed upvalues and gray strings.
• Fixed side exit jump target patching with regard to the range values of a particular instruction (gh-6098).
• Fixed the issue on ARM64 where the current Lua coroutine wasn’t restored on the exceptional path (gh-6189).

Now the memory profiler records allocations from traces, grouping them by the trace number (gh-5814). The memory profiler parser can display the new type of allocation sources in the following format:

| TRACE [<trace-no>] <trace-addr> started at @<sym-chunk>:<sym-line>

Descriptions of type mismatch error and inconsistent type error have become more informative (gh-6176).

Removed explicit cast from BOOLEAN to numeric types and vice versa (gh-4770).

For example, CAST(FALSE AS INTEGER) was 0 in version 2.8. Now it causes an error.

Removed explicit cast from VARBINARY to 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.

Now a numeric value can be cast to another numeric type only if the cast is precise. In addition, a UUID value cannot be implicitly cast to STRING/VARBINARY. Also, a STRING/VARBINARY value cannot be implicitly cast to a UUID (gh-4470).

Now any number can be compared to any other number, and values of any scalar type can be compared to any other value of the same type. A value of a non-numeric scalar type cannot be compared with a value of any other scalar type (gh-4230).

Removed SQL built-in functions from the _func system space (gh-6106).

The function is now looked up first in SQL built-in functions and then in user-defined functions.

Fixed incorrect error message in case of misuse of the function setting the default value.

The TYPEOF() function with NULL as an argument now returns NULL (gh-5956).

Reworked the SCALAR and NUMBER types in SQL. Removed the implicit cast from SCALAR to any other scalar type. Also, removed the implicit cast from NUMBER values to any other numeric type. It means that arithmetic and bitwise operations and concatenation are no longer allowed for SCALAR and NUMBER values. In addition, any SCALAR value can now be compared with values of any other scalar type using the SCALAR rules (gh-6221).

The field type DECIMAL is now available in SQL. Added an implicit cast from INTEGER and DOUBLE to DECIMAL and vice versa. DECIMAL can participate in arithmetic operations and comparisons with other defined numeric types (gh-4415).

The argument types of SQL built-in functions are now checked in most cases during parsing. In addition, the number of arguments is now always checked during parsing (gh-6105).

Now DECIMAL values can be bound in SQL (gh-4717).

A value consisting of digits and a decimal point is now parsed as DECIMAL (gh-6456).

The field type ANY is now available in SQL (gh-3174).

Built-in SQL functions now work correctly with DECIMAL values (gh-6355).

A default type is now defined in case the argument type of a SQL built-in function cannot be determined during parsing (gh-4415).

The field type ARRAY is now available in SQL. The syntax has also been implemented to allow the creation of ARRAY values (gh-4762).

[Breaking change] 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:

in C:

fiber_wakeup(fiber_self());
fiber_yield();

and in Lua:

fiber.self():wakeup()
fiber.yield()

To get the same effect in C, one can 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 box.on_commit() and box.on_rollback() (gh-6025).

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 .xlog files 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.cfg call even if an empty .xlog was 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) .xlog file (gh-5979).

The counter in N rows processed log messages no longer resets on each newly recovered xlog.

Fixed wrong type specification when printing fiber state change. It could lead to negative fiber IDs in the logs (gh-5846).

For example,

main/-244760339/cartridge.failover.task I> Instance state changed

instead of proper

main/4050206957/cartridge.failover.task I> Instance state changed

Fiber IDs are now switched switched to monotonically increasing unsigned 8-byte integers, so there is no ID wrapping anymore. It allows detecting fiber precedence by ID (gh-5846).

Fixed a crash in JSON update on tuple/space, where the update included two or more operations that accessed fields in reversed order and these fields didn’t exist. Example: box.tuple.new({1}):update({{'=', 4, 4}, {'=', 3, 3}}) (gh-6069).

Fixed invalid results of the json module’s encode function when it was used from the Lua garbage collector. For example, this could happen in functions used as ffi.gc() (gh-6050).

Added a check for user input of the number of iproto threads: value must be greater than zero and less than or equal to 1000 (gh-6005).

Fixed error related to the fact that if user changed listen address, all iproto threads closed same socket multiple times. Fixed error, related to the fact, that tarantool not deleting the unix socket path, when it’s finishing work.

Simultaneously updating a key in different transactions does not longer result in a MVCC crash (gh-6131).

Fix a bug when memtx MVCC crashed during reading uncommitted DDL (gh-5515).

Fixed a bug when memtx MVCC crashed if an index was created in the transaction (gh-6137).

Fixed a MVCC segmentation fault that arose when updating the entire space concurrently (gh-5892).

Fixed a bug with failed assertion after a stress update of the same key (gh-6193).

Fixed a crash where box.snapshot could be called during an incomplete transaction (gh-6229).

Fixed console client connection failure in case of request time out (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).

box.info.uuid, box.info.cluster.uuid, and tostring(decimal) with any decimal number in Lua could sometimes return garbage if there were __gc handlers 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 select{} hash (gh-6040).

Fixed a crash in MVCC after a drop of space with several indexes (gh-6274).

Fixed a bug when the GC could leave tuples in secondary indexes (gh-6234).

Disallowed 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 connected that happened on rollback after a DDL operation (gh-5998).

Fixed a bug when rollback resulted in unserializable behaviour (gh-6325)

Previously, when a net.box connection was closed, all requests that had not been sent were discarded. This patch fixed this behavior: all requests queued for sending before the connection is closed are guaranteed to be sent (gh-6338).

Fixed a crash during replace of malformed tuple into _schema system space (gh-6332).

Fixed dropping incoming messages when connection is closed or SHUT_RDWR received and net_msg_max or readahead limit is reached (gh-6292).

Fixed memory leak in case of replace during background alter of primary index (gh-6290)

Fixed a bug when rollbacked changes appears in built-in-background index (gh-5958).

Fixed a crash while encoding an error object in the MsgPack format (gh-6431).

Fixed a bug when index was inconsistent after background build in case when the primary index is hash (gh-5977).

Now inserting a tuple with the wrong id field into the _priv space will return the correct error (gh-6295).

Fixed dirty read in MVCC after space alter (gh-6263, gh-6318).

Fixed crash in case a fiber changing box.cfg.listen is woken up (gh-6480).

Fixed box.cfg.listen not reverted to the old address in case the new one is invalid (gh-6092).

Fixed a crash caused by a race between box.session.push() and closing connection (gh-6520).

Fixed a bug because of which the garbage collector could remove an xlog file that is still in use (gh-6554).

Fixed a crash during granting privileges from guest (gh-5389).

Fixed an error in listening when user pass uri in numerical form after listening unix socket (gh-6535).

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 a TOO_EARLY_SUBSCRIBE error (gh-6094).

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 disk regardless 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_MSGPACK when the replica is under high load (gh-4040).

Fixed a cluster sometimes being unable to bootstrap if it contains nodes with election_mode set to manual or voter (gh-6018).

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 to a 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 replica reconnecting to a living master on any box.cfg{replication=...} change. Such reconnects could result in replica failure to restore connection for replication_timeout seconds (gh-4669).