From: Alexander Turenko <alexander.turenko@tarantool.org>
To: "Alexander V. Tikhonov" <avtikhon@tarantool.org>
Cc: Oleg Piskunov <o.piskunov@tarantool.org>,
tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v1] test: fix flaky replication/wal_off.test.lua
Date: Tue, 23 Jun 2020 17:11:53 +0300 [thread overview]
Message-ID: <20200623141153.54zcj2jxhpy3ajf3@tkn_work_nb> (raw)
In-Reply-To: <1b3fbd233b491ed1ea5f08bde5717918a9a72a57.1591727784.git.avtikhon@tarantool.org>
On Fri, Jun 19, 2020 at 02:48:23PM +0300, Alexander V. Tikhonov wrote:
> Found issue:
>
> [003] --- replication/wal_off.result Thu Apr 25 13:10:18 2019
> [003] +++ replication/wal_off.reject Tue Jul 16 17:10:31 2019
> [003] @@ -95,6 +95,8 @@
> [003] ...
> [003] while string.find(box.info.replication[wal_off_id].upstream.message, check) == nil do fiber.sleep(0.01) end
> [003] ---
> [003] +- error: '[string "while string.find(box.info.replication[wal_of..."]:1: bad argument
> [003] + #1 to ''find'' (string expected, got nil)'
> [003] ...
> [003] box.cfg { replication = "" }
> [003] ---
>
> To check the upstream status and it's message need to wait until an
> upstream appears. This prevents an attempt to index a nil value when
> one of those functions are called before a record about a peer appears
> in box.info.replication. It was observed on test:
> replication/show_error_on_disconnect
> after commit
> c6bea65f8ef5f6c737cf70c0127189d0ebcbc36e ('replication: recfg with 0
> quorum returns immediately').
>
> Closes #4355
> ---
>
> Github: https://github.com/tarantool/tarantool/tree/avtikhon/gh-4355-replication-wall-off
> Issue: https://github.com/tarantool/tarantool/issues/4355
LGTM.
next prev parent reply other threads:[~2020-06-23 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 11:48 Alexander V. Tikhonov
2020-06-23 14:11 ` Alexander Turenko [this message]
2020-06-26 9:27 ` Kirill Yukhin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200623141153.54zcj2jxhpy3ajf3@tkn_work_nb \
--to=alexander.turenko@tarantool.org \
--cc=avtikhon@tarantool.org \
--cc=o.piskunov@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v1] test: fix flaky replication/wal_off.test.lua' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox