Tarantool 1.10.3 LTS released

11 views
Skip to first unread message

Кирилл Юхин

unread,
Apr 1, 2019, 5:02:39 AM4/1/19
to tarantool-ru
Date: 2019-04-01

Tag: 1.10.3-0-g0b7078a

Overview

1.10.3 is the next stable release in the 1.10 series. The label 'stable' means we have had systems running in production without known crashes, bad results or other showstopper bugs for quite a while now.

This release resolves 69 issues since 1.10.2. There may be bugs in less common areas, please feel free to
file an issue at GitHub.

Compatibility

Tarantool 1.10.x is backward compatible with Tarantool 1.9.x in 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 1.10.x series when migrating from 1.9 version.

Functionality added or changed

Engines

  • Randomize vinyl index compaction gh-3944
  • Throttle tx thread if compaction doesn't keep up with dumps gh-3721
  • Do not apply run_count_per_level to the last level gh-3657

Server

  • Report the number of active iproto connections gh-3905

Replication

  • Never keep a dead replica around if running out of disk space gh-3397
  • Report join progress to the replica log gh-3165

Lua

Bugs fixed

Engines

  • Tarantool crashes if DML races with DDL gh-3420
  • Recovery error if DDL is aborted gh-4066
  • Tarantool could commit in the read-only mode gh-4016
  • Vinyl iterator crashes if used throughout DDL gh-4000
  • Vinyl doesn't exit until dump/compaction is complete gh-3949
  • After re-creating secondary index no data is visible gh-3903
  • box.info.memory().tx underflow gh-3897
  • Vinyl stalls on intensive random insertion gh-3603

Server

  • Newer version of libcurl explodes fiber stack gh-3569
  • SIGHUP crashes tarantool gh-4063
  • checkpoint_daemon.lua:49: bad argument #2 to 'format' gh-4030
  • fiber:name() show only part of name gh-4011
  • Second hot standby switch may fail gh-3967
  • Updating box.cfg.readahead doesn't affect existing connections gh-3958
  • fiber.join() blocks in 'suspended' if fiber has cancelled gh-3948
  • Tarantool can be crashed by sending gibberish to a binary socket gh-3900
  • Stored procedure to produce push-messages never breaks on client disconnect gh-3859
  • Tarantool crashed in lj_vm_return gh-3840
  • Fiber executing box.cfg() may process messages from iproto gh-3779
  • Possible regression on nosqlbench gh-3747
  • Assertion after improper index creation gh-3744
  • Tarantool crashes on vshard startup (lj_gc_step) gh-3725
  • Do not restart replication on box.cfg if the configuration didn't change gh-3711

Replication

  • Applier times out too fast when reading large tuples gh-4042
  • Vinyl replica join fails gh-3968
  • Error during replication gh-3910
  • Downstream status doesn't show up in replication.info unless the channel is broken gh-3904
  • replication fails: tx checksum mismatch gh-3883
  • Rebootstrap crashes if master has replica's rows gh-3740
  • After restart tuples revert back to their old state which was before replica sync gh-3722
  • Add vclock for safer hot standby switch gh-3002
  • Master row is skipped forever in case of wal write failure gh-2283

Lua

  • space:frommap():tomap() conversion fail gh-4045
  • Non-informative message when trying to read a negative count of bytes from socket gh-3979
  • space:frommap raise "tuple field does not match..." even for nullable field gh-3883
  • Tarantool crashes on net.box.call after some uptime with vshard internal fiber gh-3751
  • Heap use after free in lbox_error gh-1955

Misc

  • http.client doesn't honour 'connection: keep-alive' gh-3955
  • net.box wait_connected is broken gh-3856
  • Mac build fails on Mojave gh-3797
  • FreeBSD build error: no SSL support gh-3750
  • 'http.client' sets invalid (?) reason gh-3681
  • Http client silently modifies headers when value is not a "string" or a "number" gh-3679
  • yaml.encode uses multiline format for 'false' and 'true' gh-3662
  • yaml.encode encodes 'null' incorrectly gh-3583
  • Error object message is empty gh-3604
  • Log can be flooded by warning messages gh-2218
Reply all
Reply to author
Forward
0 new messages