From: Vladislav Shpilevoy via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Sergey Petrenko <sergepetrenko@tarantool.org>, tarantool-patches@dev.tarantool.org, gorcunov@gmail.com Subject: Re: [Tarantool-patches] [PATCH 1/1] election: fix box.ctl.promote() crash on 0 LSN Date: Mon, 26 Jul 2021 23:54:20 +0200 [thread overview] Message-ID: <dc17f701-4340-d6f9-7038-6f4e460982e6@tarantool.org> (raw) In-Reply-To: <d6d6d248-28ab-79d5-c157-0f75c04ef67a@tarantool.org> Thanks for the review! >> diff --git a/test/replication/gh-5430-master3.lua b/test/replication/gh-5430-master3.lua >> new file mode 100644 >> index 000000000..eff479a68 >> --- /dev/null >> +++ b/test/replication/gh-5430-master3.lua >> @@ -0,0 +1,12 @@ >> +#!/usr/bin/env tarantool >> + >> +require('console').listen(os.getenv('ADMIN')) >> + >> +box.cfg({ >> + listen = 'unix/:./master3.sock', >> + replication = { >> + 'unix/:./master1.sock', >> + }, >> + replication_synchro_quorum = 3, >> + replication_timeout = 0.5, >> +}) > > > I'd create a single lua file, gh-5430-master.lua, and 3 symlinks. > > listening socket may be deduced from filename, and > > replication_synchro_quorum might be passed as a parameter. Too many differences. I need a grant in one master, ready_only in another master, different quorum and replication in the third master. I don't like how these monstrous files look in the end having all these symbolic links at them. Here it is a bit of code duplication, but you can always easily say which node how is configured. > I don't insist, LGTM anyways. Pushed to master, 2.8, 2.7.
prev parent reply other threads:[~2021-07-26 21:54 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-22 23:31 Vladislav Shpilevoy via Tarantool-patches 2021-07-25 17:41 ` Sergey Petrenko via Tarantool-patches 2021-07-26 21:54 ` Vladislav Shpilevoy via Tarantool-patches [this message]
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=dc17f701-4340-d6f9-7038-6f4e460982e6@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=gorcunov@gmail.com \ --cc=sergepetrenko@tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 1/1] election: fix box.ctl.promote() crash on 0 LSN' \ /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