From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: sergeyb@tarantool.org, tarantool-patches@dev.tarantool.org,
sergepetrenko@tarantool.org, gorcunov@gmail.com,
lvasiliev@tarantool.org
Subject: Re: [Tarantool-patches] [PATCH 3/3] replication: add test with random leaders promotion and demotion
Date: Thu, 9 Jul 2020 22:07:33 +0200 [thread overview]
Message-ID: <b509a4cf-bcc9-e9ce-98cc-13e656526694@tarantool.org> (raw)
In-Reply-To: <b6a0c7b42d71fd263c51d44c96748587092dda1e.1594314820.git.sergeyb@tarantool.org>
Привет!
On 09/07/2020 19:16, sergeyb@tarantool.org wrote:
> From: Sergey Bronnikov <sergeyb@tarantool.org>
>
> Part of #5055
> ---
> test/replication/qsync.lua | 62 ++++++++++
> test/replication/qsync1.lua | 1 +
> test/replication/qsync10.lua | 1 +
> test/replication/qsync11.lua | 1 +
> test/replication/qsync12.lua | 1 +
> test/replication/qsync13.lua | 1 +
> test/replication/qsync14.lua | 1 +
> test/replication/qsync15.lua | 1 +
> test/replication/qsync16.lua | 1 +
> test/replication/qsync17.lua | 1 +
> test/replication/qsync18.lua | 1 +
> test/replication/qsync19.lua | 1 +
> test/replication/qsync2.lua | 1 +
> test/replication/qsync20.lua | 1 +
> test/replication/qsync21.lua | 1 +
> test/replication/qsync22.lua | 1 +
> test/replication/qsync23.lua | 1 +
> test/replication/qsync24.lua | 1 +
> test/replication/qsync25.lua | 1 +
> test/replication/qsync26.lua | 1 +
> test/replication/qsync27.lua | 1 +
> test/replication/qsync28.lua | 1 +
> test/replication/qsync29.lua | 1 +
> test/replication/qsync3.lua | 1 +
> test/replication/qsync30.lua | 1 +
> test/replication/qsync31.lua | 1 +
> test/replication/qsync4.lua | 1 +
> test/replication/qsync5.lua | 1 +
> test/replication/qsync6.lua | 1 +
> test/replication/qsync7.lua | 1 +
> test/replication/qsync8.lua | 1 +
> test/replication/qsync9.lua | 1 +
Патч я еще не смотрел нормально, но блин, это перебор. Не надо 30 реплик
стартовать плиз. Хватит 5 максимум. И между ними рандомно попрыгать.
Как такой тест отлаживать в случае чего, я не представляю. Как и
насколько долго он работает.
next prev parent reply other threads:[~2020-07-09 20:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1594314820.git.sergeyb@tarantool.org>
2020-07-09 17:16 ` [Tarantool-patches] [PATCH 1/3] replication: print number of txs in limbo before its clear sergeyb
2020-07-09 20:07 ` Vladislav Shpilevoy
2020-07-10 12:55 ` Sergey Bronnikov
2020-07-20 21:59 ` Vladislav Shpilevoy
2020-07-09 17:16 ` [Tarantool-patches] [PATCH 2/3] replication: test clear_synchro_queue function sergeyb
2020-07-20 22:00 ` Vladislav Shpilevoy
2020-08-25 12:49 ` Sergey Bronnikov
2020-08-26 7:31 ` Serge Petrenko
2020-08-26 14:48 ` Sergey Bronnikov
2020-07-09 17:16 ` [Tarantool-patches] [PATCH 3/3] replication: add test with random leaders promotion and demotion sergeyb
2020-07-09 20:07 ` Vladislav Shpilevoy [this message]
2020-07-10 8:05 ` Sergey Bronnikov
2020-07-20 22:01 ` Vladislav Shpilevoy
2020-08-26 14:45 ` Sergey Bronnikov
2020-08-27 10:49 ` Serge Petrenko
2020-08-31 10:05 ` Sergey Bronnikov
2020-09-01 13:03 ` Serge Petrenko
2020-11-12 9:32 ` Sergey Bronnikov
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=b509a4cf-bcc9-e9ce-98cc-13e656526694@tarantool.org \
--to=v.shpilevoy@tarantool.org \
--cc=gorcunov@gmail.com \
--cc=lvasiliev@tarantool.org \
--cc=sergepetrenko@tarantool.org \
--cc=sergeyb@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH 3/3] replication: add test with random leaders promotion and demotion' \
/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