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 1/2] replication: introduce ballot.can_be_leader
Date: Fri, 16 Jul 2021 17:29:59 +0300 [thread overview]
Message-ID: <20210716142959.GC146960@starling> (raw)
In-Reply-To: <0c92a88ff1d392f8b03de59be8cb19a162bf78f8.1626392372.git.v.shpilevoy@tarantool.org>
* Vladislav Shpilevoy via Tarantool-patches <tarantool-patches@dev.tarantool.org> [21/07/16 11:23]:
> The flag tells whether the sender has election mode 'candidate' or
> 'manual'.
>
> The new field during bootstrap will help to avoid selecting a
> 'voter' as a master. Voters can't write, they are unable to boot
> themselves nor register others.
>
> @TarantoolBot document
> Title: New field - IPROTO_BALLOT_CAN_BE_LEADER
> It is sent as a part of `IPROTO_BALLOT (0x29)`. The field is a
> boolean flag which is true if the sender has `election_mode` in
> its config `'manual'` or `'candidate'`.
>
> During bootstrap the nodes able to become a leader are preferred
> over the nodes configured as `'voter'`.
Curious why did you add this feature in the first place, I mean
"eligibility"? Each voter has to be able to become a leader,
otherwise raft liveness guarantees are violated. Raft has
learners, but learners neither vote nor can become leaders.
--
Konstantin Osipov, Moscow, Russia
next prev parent reply other threads:[~2021-07-16 14:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 23:49 [Tarantool-patches] [PATCH 0/2] Bootstrap voter Vladislav Shpilevoy via Tarantool-patches
2021-07-15 23:49 ` [Tarantool-patches] [PATCH 1/2] replication: introduce ballot.can_be_leader Vladislav Shpilevoy via Tarantool-patches
2021-07-16 10:59 ` Serge Petrenko via Tarantool-patches
2021-07-18 17:00 ` Vladislav Shpilevoy via Tarantool-patches
2021-07-19 9:11 ` Sergey Petrenko via Tarantool-patches
2021-07-16 14:29 ` Konstantin Osipov via Tarantool-patches [this message]
2021-07-18 17:00 ` Vladislav Shpilevoy via Tarantool-patches
2021-07-19 9:12 ` Konstantin Osipov via Tarantool-patches
2021-07-19 22:06 ` Vladislav Shpilevoy via Tarantool-patches
2021-07-20 8:49 ` Konstantin Osipov via Tarantool-patches
2021-07-20 20:02 ` Vladislav Shpilevoy via Tarantool-patches
2021-07-20 20:18 ` Konstantin Osipov via Tarantool-patches
2021-07-20 21:16 ` Cyrill Gorcunov via Tarantool-patches
2021-07-20 23:20 ` Konstantin Osipov via Tarantool-patches
2021-07-21 18:51 ` Cyrill Gorcunov via Tarantool-patches
2021-07-21 21:43 ` Vladislav Shpilevoy via Tarantool-patches
2021-07-15 23:49 ` [Tarantool-patches] [PATCH 2/2] election: during bootstrap prefer candidates Vladislav Shpilevoy via Tarantool-patches
2021-07-16 11:30 ` Serge Petrenko via Tarantool-patches
2021-07-18 17:00 ` Vladislav Shpilevoy via Tarantool-patches
2021-07-16 14:27 ` [Tarantool-patches] [PATCH 0/2] Bootstrap voter Konstantin Osipov via Tarantool-patches
2021-07-18 17:00 ` Vladislav Shpilevoy via Tarantool-patches
2021-07-19 9:13 ` Konstantin Osipov via Tarantool-patches
2021-07-19 22:04 ` Vladislav Shpilevoy 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=20210716142959.GC146960@starling \
--to=tarantool-patches@dev.tarantool.org \
--cc=kostja.osipov@gmail.com \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH 1/2] replication: introduce ballot.can_be_leader' \
/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