From: Serge Petrenko <sergepetrenko@tarantool.org> To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>, tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH 0/3] Raft follow-ups Date: Mon, 28 Sep 2020 10:09:31 +0300 [thread overview] Message-ID: <31234cb7-cd07-d3c9-2a23-e6aed56ab669@tarantool.org> (raw) In-Reply-To: <cover.1601069274.git.v.shpilevoy@tarantool.org> 26.09.2020 00:29, Vladislav Shpilevoy пишет: > The patchset is a couple of fixes for the existing Raft code, and > also a new leader election policy - the third patch makes so an > instance restart does not lead to a new election immediately > anymore. > > See the commit message and comments why. > > Branch: http://github.com/tarantool/tarantool/tree/gh-1146-raft > Issue: https://github.com/tarantool/tarantool/issues/1146 > > Vladislav Shpilevoy (3): > [tosquash] raft: vote without a new term when possible > [tosquash] raft: fix 99% CPU issue in raft io worker > [tosquash] raft: don't start new election immediately after restart > > src/box/box.cc | 12 ++++++++++- > src/box/raft.c | 54 +++++++++++++++++++++++++++++++++++++++++++------- > src/box/raft.h | 8 ++++++++ > 3 files changed, 66 insertions(+), 8 deletions(-) Hi! Thanks for the fixes! The patchset LGTM. > -- Serge Petrenko
prev parent reply other threads:[~2020-09-28 7:09 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-25 21:29 Vladislav Shpilevoy 2020-09-25 21:29 ` [Tarantool-patches] [PATCH 1/3] [tosquash] raft: vote without a new term when possible Vladislav Shpilevoy 2020-09-25 21:29 ` [Tarantool-patches] [PATCH 2/3] [tosquash] raft: fix 99% CPU issue in raft io worker Vladislav Shpilevoy 2020-09-25 21:29 ` [Tarantool-patches] [PATCH 3/3] [tosquash] raft: don't start new election immediately after restart Vladislav Shpilevoy 2020-09-28 7:09 ` Serge Petrenko [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=31234cb7-cd07-d3c9-2a23-e6aed56ab669@tarantool.org \ --to=sergepetrenko@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 0/3] Raft follow-ups' \ /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