Release 1.4.0

[oleg-jukovec]

The release introduces an experimental storage_mode option for the utube and utubettl drivers with the memtx engine. It could be used to create a utube or utubettl queue with an additional buffer space that stores only ready to take tasks.

local tube = queue.create_tube('utube_with_ready_buffer', 'utube',
    {storage_mode = queue.driver.utube.STORAGE_MODE_READY_BUFFER})

local tube = queue.create_tube('utubettl_with_ready_buffer', 'utubettl',
    {storage_mode = queue.driver.utubettl.STORAGE_MODE_READY_BUFFER})

The storage mode slower in general cases, but a much faster in cases when you have utubes with many tasks (see README.md for the performance comparison). So you should make your choice carefully.

Added

• Experimental storage_mode option for creating a utube and utubettl tube (#228). It enables the workaround for slow takes while working with busy tubes.

Fixed

• Stuck in INIT state if an instance failed to enter the running mode in time (#226). This fix works only for Tarantool versions >= 2.10.0.
• Slow takes on busy utube and utubettl tubes (#228). The workaround could be enabled by passing the storage_mode = "ready_buffer" option while creating the tube.

[DifferentialOrange]

Isn't it more like 1.4.0?

[oleg-jukovec]

https://semver.org/spec/v2.0.0.html

Patch version Z (x.y.Z | x > 0) MUST be incremented if only backward compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.

Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backward compatible functionality is introduced to the public API. It MUST be incremented if any public API functionality is marked as deprecated. It MAY be incremented if substantial new functionality or improvements are introduced within the private code. It MAY include patch level changes. Patch version MUST be reset to 0 when minor version is incremented.

It seems we need 1.4.0.

[oleg-jukovec]

Isn't it more like 1.4.0?

Thank you, updated.