From: Konstantin Osipov via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH 0/4] Split vote
Date: Tue, 18 Jan 2022 10:18:20 +0300 [thread overview]
Message-ID: <20220118071820.GA894591@starling> (raw)
In-Reply-To: <710d8863-afa3-f8ba-7f11-f5c6fadd8882@tarantool.org>
* Vladislav Shpilevoy <v.shpilevoy@tarantool.org> [22/01/18 02:16]:
> >> Split vote handling in Raft, its usage in storage, and a bug fix found while
> >> working on this in the first commit.
> >>
> >> Branch: http://github.com/tarantool/tarantool/tree/gerold103/gh-5285-raft-split-vote
> >> Issue: https://github.com/tarantool/tarantool/issues/5285
> >
> > While I don't mind this patch it is an unnecessary complication on
> > top of the spec. To prevent the deteriorating effects on liveness
> > from split vote one needs pre-voting, not split-vote detection.
>
> I agree. I also don't like that patchset too much (not counting the first
> commit, which fixes a crash). The pros are:
>
> - can save some seconds in case of a split-vote;
>
> - potentially can expose all the vote counts to the monitoring, not
> just own count.
>
> Cons is - too much hassle in the code just for that.
>
> Pre-voting on the other hand solves a different problem. Only slightly
> related.
Well, I don't doubt this hassle is not too harmful to the logic of
the protocol, but it's not solving all the liveness issues either.
--
Konstantin Osipov, Moscow, Russia
prev parent reply other threads:[~2022-01-18 7:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 0:48 Vladislav Shpilevoy via Tarantool-patches
2022-01-15 0:48 ` [Tarantool-patches] [PATCH 1/4] raft: fix crash on election_timeout reconfig Vladislav Shpilevoy via Tarantool-patches
2022-01-18 13:12 ` Serge Petrenko via Tarantool-patches
2022-01-15 0:48 ` [Tarantool-patches] [PATCH 2/4] raft: track all votes, even not own Vladislav Shpilevoy via Tarantool-patches
2022-01-21 0:42 ` Vladislav Shpilevoy via Tarantool-patches
2022-01-15 0:48 ` [Tarantool-patches] [PATCH 3/4] raft: introduce split vote detection Vladislav Shpilevoy via Tarantool-patches
2022-01-18 13:20 ` Serge Petrenko via Tarantool-patches
2022-01-20 0:44 ` Vladislav Shpilevoy via Tarantool-patches
2022-01-20 10:21 ` Serge Petrenko via Tarantool-patches
2022-01-20 23:02 ` Vladislav Shpilevoy via Tarantool-patches
2022-01-15 0:48 ` [Tarantool-patches] [PATCH 4/4] election: activate raft split vote handling Vladislav Shpilevoy via Tarantool-patches
2022-01-18 13:21 ` Serge Petrenko via Tarantool-patches
2022-01-20 0:44 ` Vladislav Shpilevoy via Tarantool-patches
2022-01-16 14:10 ` [Tarantool-patches] [PATCH 0/4] Split vote Konstantin Osipov via Tarantool-patches
2022-01-17 22:57 ` Vladislav Shpilevoy via Tarantool-patches
2022-01-18 7:18 ` Konstantin Osipov 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=20220118071820.GA894591@starling \
--to=tarantool-patches@dev.tarantool.org \
--cc=kostja.osipov@gmail.com \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH 0/4] Split vote' \
/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