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: Sun, 16 Jan 2022 17:10:13 +0300 [thread overview]
Message-ID: <20220116141013.GA121005@starling> (raw)
In-Reply-To: <cover.1642207647.git.v.shpilevoy@tarantool.org>
* Vladislav Shpilevoy via Tarantool-patches <tarantool-patches@dev.tarantool.org> [22/01/15 03:52]:
> 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.
> Vladislav Shpilevoy (4):
> raft: fix crash on election_timeout reconfig
> raft: track all votes, even not own
> raft: introduce split vote detection
> election: activate raft split vote handling
--
Konstantin Osipov, Moscow, Russia
next prev parent reply other threads:[~2022-01-16 14:10 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 ` Konstantin Osipov via Tarantool-patches [this message]
2022-01-17 22:57 ` [Tarantool-patches] [PATCH 0/4] Split vote Vladislav Shpilevoy via Tarantool-patches
2022-01-18 7:18 ` Konstantin Osipov via Tarantool-patches
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=20220116141013.GA121005@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