Commits


lua: support conf module in command-line options Attention: Patch contains a breaking change - default behaviour in tarantool is changed: by default "tarantool" command prints a usage and don't run a Lua interpeter. 1. https://github.com/tarantool/conf Closes #8613 @TarantoolBot document Title: introduce cli options for conf module Previously tarantool entered to interactive mode by starting Lua interpreter. Now 'tarantool' command prints a usage and don't run a Lua interpeter. Two new options were added: --name (-n) and --config (-c).


lua: embed conf module tarantool/conf [1] is a Lua module for configuring tarantool instance. Proposed patch embeds conf module to tarantool and adds regression tests for conf module. 1. https://github.com/tarantool/conf Part of #8613 @TarantoolBot document Title: embedded conf module Now tarantool has a conf module on its board. conf is a Lua module which is widely used by Tarantool users for configuration clusters with Tarantool instances.


static-build: enable compiler optimizations for dependencies An autoconf-generated configure script doesn't enable compiler optimization flags if CFLAGS / CXXFLAGS options are set explicitly. We started setting CFLAGS / CXXFLAGS in commit e6abe1c91ae3 ("cmake: add extra security compiler options"). As a result, users started experiencing performance degradation issues, like the one described in tarantool/tarantool-ee#440. Let's set -O2 in CFLAGS / CXXFLAGS explicitly to fix that. Closes #8606 Needed for tarantool/tarantool-ee#440 NO_DOC=build NO_TEST=build


lua: implement stubs for etcd client To enable etcd client set the following CMake variables: - ENABLE_ETCD_CLIENT: ON - ETCD_CLIENT_DIR: path to a directory with etcd client Lua source files If ENABLE_ETCD_CLIENT is unset, then a stub implementation is built, which spits an error on attempt require etcd-client. Needed for https://github.com/tarantool/tarantool-ee/issues/443 MSG="stubs for enterprise version, no user-visible changes" NO_CHANGELOG=MSG NO_DOC=MSG NO_TEST=MSG


test: re-enable linearizable test after fix The test flaked a lot on FreeBSD and Mac OS due to some proxy problems which were fixed in scope of tarantool/luatest@5b704ac. Another possible failure looked like this: NO_WRAP [006] not ok 5 linearizable-read.test_leader_change [006] # Can't modify data on a read-only instance - it is an orphan [006] # stack traceback: [006] # ...tarantool/test/replication-luatest/linearizable_test.lua:196: in function 'linearizable-read.test_leader_change' [006] # ... [006] # [C]: in function 'xpcall' NO_WRAP Fix it by waiting for the server to follow its upstreams. Closes tarantool/tarantool-qa#277 NO_DOC=test fix NO_CHANGELOG=test fix