Yaroslav Dynnikov authored 2 years ago and Yaroslav Dynnikov committed 2 years ago

These libs installed in Dockerfile aren't used for the build. Instead,
tarantool is built with sources from `vendored` directory.

Also prefix stored procedures names `raft_join` and `raft_interact`

Yaroslav Dynnikov authored 2 years ago and Yaroslav Dynnikov committed 2 years ago

The error message about `on_shutdown` trigger failure recently changed
in tarantool [1]. Our test doesn't catch it anymore.

- [1] https://github.com/tarantool/tarantool/commit/ca59d3050c

When instance runs `postjoin` function, it's supposed to have both
target and current grade Offline. Taking a read barrier in that state
makes no sence. Instead, an instance should set target grade online
asap. Ensuring it syncs is the responsibility of the governor.

Excessive read barrier affects `restart_both` test. One of the instances
(i1 who becomes a follower) sends a `read_index` request to i2 (leader).
But i2 reveals  `self.commit_to_current_term()` condition isn't met and
drops the request. As a result, i1 is obliged to wait for 10s timeout
before retrying `read_index` request again, but the test timeouts even
sooner.

An important test case (5b5d25f3) went missing after migration from
luatest to pytest (b6630a41).

Conftest operates subprocesses in a different way than luatest helpers
did: luatest used to signal a signal process (supervisor), while
`instance.kill()` signals the whole process group.