From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: "Alexander V. Tikhonov" <avtikhon@tarantool.org>, Kirill Yukhin <kyukhin@tarantool.org>, Serge Petrenko <sergepetrenko@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH v1] test: flaky replication/gh-5195-qsync-* Date: Wed, 9 Sep 2020 23:12:40 +0200 [thread overview] Message-ID: <c4f8baf6-a284-feb5-eed3-68a309a5f533@tarantool.org> (raw) In-Reply-To: <0e6d058ce43dcba3b8268a1a09e71e22e287a7db.1599480747.git.avtikhon@tarantool.org> Thanks for the patch! See 3 comments below. On 07.09.2020 14:13, Alexander V. Tikhonov wrote: > On heavy loaded hosts found the following issue: > > box.cfg{replication_synchro_quorum = 2} > | --- > + | - error: '[string "test_run:wait_cond(function() ..."]:1: attempt to > + | index field ''vclock'' (a nil value)' 1. How is that output possible? box.cfg has nothing to do with wait_cond nor with vclocks. The diff looks broken, misplaced. > | ... > test_run:wait_cond(function() return f:status() == 'dead' end) > | --- > - | - true > + | - false > | ... > ok, err > | --- > - | - true > - | - [2] > + | - null > + | - null > | ... > box.space.sync:select{} > | --- > > It happened because replication vclock field was not exist at the moment > of its check. To fix the issue, vclock field had to be waited to be > available using test_run:wait_cond() routine. 2. But in the fix you don't wait for it. You just added one more level of checking inside the existing wait_cond. > Closes #5230 > --- > > Github: https://github.com/tarantool/tarantool/tree/avtikhon/gh-5230-fix-qsync-write-5195 > Issue: https://github.com/tarantool/tarantool/issues/5230 > > test/replication/gh-5195-qsync-replica-write.result | 10 ++++++---- > test/replication/gh-5195-qsync-replica-write.test.lua | 7 +++---- > 2 files changed, 9 insertions(+), 8 deletions(-) > > diff --git a/test/replication/gh-5195-qsync-replica-write.result b/test/replication/gh-5195-qsync-replica-write.result > index 3999e8f5e..b47359fde 100644 > --- a/test/replication/gh-5195-qsync-replica-write.result > +++ b/test/replication/gh-5195-qsync-replica-write.result > @@ -96,10 +96,12 @@ test_run:wait_downstream(replica_id, {status='follow'}) > | - true > | ... > test_run:wait_cond(function() \ > - local info = box.info.replication[replica_id] \ > - local lsn = info.downstream.vclock[replica_id] \ > - return lsn and lsn >= replica_lsn \ > -end) \ > + local lsn = box.info.replication[replica_id].downstream.vclock \ 3. It is not lsn, it is vclock now. Also I don't think you need to inline 'info' variable, it was perfectly fine. > + return (lsn and lsn[replica_id] and lsn[replica_id] >= replica_lsn) \ > + end) or box.info > + | --- > + | - true > + | ...
next prev parent reply other threads:[~2020-09-09 21:12 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-07 12:13 Alexander V. Tikhonov 2020-09-09 15:45 ` Serge Petrenko 2020-09-09 21:12 ` Vladislav Shpilevoy [this message] 2020-09-10 8:13 ` Alexander V. Tikhonov 2020-09-10 19:21 ` Vladislav Shpilevoy
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=c4f8baf6-a284-feb5-eed3-68a309a5f533@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=avtikhon@tarantool.org \ --cc=kyukhin@tarantool.org \ --cc=sergepetrenko@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v1] test: flaky replication/gh-5195-qsync-*' \ /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