From: Konstantin Osipov <kostja.osipov@gmail.com>
To: Serge Petrenko <sergepetrenko@tarantool.org>
Cc: kirichenkoga@gmail.com, tarantool-patches@dev.tarantool.org,
v.shpilevoy@tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v4 4/4] replication: do not relay rows coming from a remote instance back to it
Date: Wed, 26 Feb 2020 14:58:15 +0300 [thread overview]
Message-ID: <20200226115815.GE15433@atlas> (raw)
In-Reply-To: <1582716061.103393657@f179.i.mail.ru>
* Serge Petrenko <sergepetrenko@tarantool.org> [20/02/26 14:22]:
> I don’t think I can. The test that comes with an issue is a stress test,
> relying on running it with multiple workers simultaneously.
> It reproduces the problem when ran with 4 workers on one of my PCs,
> and with 20 workers on the other.
> I think we don’t have the appropriate testing infrastructure to run the same
> test with multiple workers at the same time, and I couldn’t come up with a
> single test which would reproduce the same problem.
Is there a place in which you can inject a sleep to make the
problem much easier to reproduce?
What about injecting a sleep in wal code on replica, the place
which increments local replicaset vclock ?
Then you will be much more likely to receive a record from the
peer before you incremented the record vclock locally, and the bug
will be reproducible with a single master.
--
Konstantin Osipov, Moscow, Russia
next prev parent reply other threads:[~2020-02-26 11:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 10:00 [Tarantool-patches] [PATCH v4 0/4] replication: fix applying of rows originating from local instance sergepetrenko
2020-02-26 10:00 ` [Tarantool-patches] [PATCH v4 1/4] box: expose box_is_orphan method sergepetrenko
2020-02-26 10:00 ` [Tarantool-patches] [PATCH v4 2/4] wal: warn when trying to write a record with a broken lsn sergepetrenko
2020-02-26 10:00 ` [Tarantool-patches] [PATCH v4 3/4] replication: implement an instance id filter for relay sergepetrenko
2020-02-26 10:18 ` Konstantin Osipov
2020-02-26 11:16 ` Serge Petrenko
2020-02-26 23:54 ` Vladislav Shpilevoy
2020-02-27 6:48 ` Konstantin Osipov
2020-02-27 13:15 ` Serge Petrenko
2020-02-27 23:33 ` Vladislav Shpilevoy
2020-02-26 10:00 ` [Tarantool-patches] [PATCH v4 4/4] replication: do not relay rows coming from a remote instance back to it sergepetrenko
2020-02-26 10:23 ` Konstantin Osipov
2020-02-26 11:21 ` Serge Petrenko
2020-02-26 11:58 ` Konstantin Osipov [this message]
2020-02-26 15:58 ` Serge Petrenko
2020-02-26 16:40 ` Konstantin Osipov
2020-02-26 23:54 ` Vladislav Shpilevoy
2020-02-27 6:52 ` Konstantin Osipov
2020-02-27 14:13 ` Serge Petrenko
2020-02-27 21:17 ` Serge Petrenko
2020-02-27 23:22 ` Vladislav Shpilevoy
2020-02-28 8:03 ` Serge Petrenko
2020-02-26 23:54 ` [Tarantool-patches] [PATCH v4 0/4] replication: fix applying of rows originating from local instance Vladislav Shpilevoy
2020-02-27 21:24 ` Serge Petrenko
2020-02-27 23:24 ` 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=20200226115815.GE15433@atlas \
--to=kostja.osipov@gmail.com \
--cc=kirichenkoga@gmail.com \
--cc=sergepetrenko@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v4 4/4] replication: do not relay rows coming from a remote instance back to it' \
/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