From: Serge Petrenko via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>, tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH 3/4] raft: introduce split vote detection Date: Thu, 20 Jan 2022 13:21:12 +0300 [thread overview] Message-ID: <9a4265d4-cc66-ad1f-5478-ebcc10eef5a8@tarantool.org> (raw) In-Reply-To: <10be2844-066e-e7fc-735a-5322fd52700e@tarantool.org> 20.01.2022 03:44, Vladislav Shpilevoy пишет: > Hi! Thanks for the review! > >>> diff --git a/src/lib/raft/raft.c b/src/lib/raft/raft.c >>> index 289d53fd5..5dcbc7821 100644 >>> --- a/src/lib/raft/raft.c >>> +++ b/src/lib/raft/raft.c >>> @@ -152,20 +152,69 @@ raft_can_vote_for(const struct raft *raft, const struct vclock *v) >>> return cmp == 0 || cmp == 1; >>> } >>> -static inline void >>> +static inline bool >>> raft_add_vote(struct raft *raft, int src, int dst) >>> { >>> struct raft_vote *v = &raft->votes[src]; >>> if (v->did_vote) >>> - return; >>> + return false; >>> v->did_vote = true; >>> ++raft->votes[dst].count; >>> + return true; >>> +} >>> + >> You may check split_vote right in raft_add_vote: >> simply track number of votes given in this term and >> max votes given for one instance. >> >> This way you won't have to run over all 32 nodes each time a vote >> is casted. > I did the fullscan intentionally. Otherwise I need to introduce 2 > new members to struct raft, keep them up to date, clear on term > bump. Too easy to miss something and introduce a bug. While in > the current version all the split-vote-specific details are in a > single function except for 'raft.votes' member. This thing I couldn't > get rid of. > > As for perf, a couple of ifs or a loop over 32 structs - both would > take order of nanoseconds anyway. Here I wouldn't bother. Simplicity > matters most. > > I did the proposal to see how it looks but then discarded as more > complex than necessary. However if you think it is still worth doing, > tell me and I will re-apply the diff. Thanks for trying this out! TBH, this diff is exactly what I wanted and it still looks better (not only preformance-wise, but simpler as well) in my opinion. I understand your point about having to update 2 extra members every now and then, so feel free to choose any option you like. > > ==================== > diff --git a/src/lib/raft/raft.c b/src/lib/raft/raft.c > index c4f5fb059..fcce3126a 100644 > --- a/src/lib/raft/raft.c > +++ b/src/lib/raft/raft.c > @@ -159,23 +159,20 @@ raft_add_vote(struct raft *raft, int src, int dst) > if (v->did_vote) > return false; > v->did_vote = true; > - ++raft->votes[dst].count; > + ++raft->voted_count; > + int count = ++raft->votes[dst].count; > + if (count > raft->max_vote_count) > + raft->max_vote_count = count; > return true; > } > > static bool > raft_has_split_vote(const struct raft *raft) > { > - int max_vote = 0; > - int vote_vac = raft->cluster_size; > - int quorum = raft->election_quorum; > - for (int i = 0; i < VCLOCK_MAX; ++i) { > - int count = raft->votes[i].count; > - vote_vac -= count; > - if (count > max_vote) > - max_vote = count; > - } > - return max_vote + vote_vac < quorum; > + int vote_vac = raft->cluster_size - raft->voted_count; > + if (vote_vac < 0) > + vote_vac = 0; > + return raft->max_vote_count + vote_vac < raft->election_quorum; > } > > static int > @@ -730,6 +727,8 @@ raft_sm_schedule_new_term(struct raft *raft, uint64_t new_term) > raft->leader = 0; > raft->state = RAFT_STATE_FOLLOWER; > memset(raft->votes, 0, sizeof(raft->votes)); > + raft->max_vote_count = 0; > + raft->voted_count = 0; > /* > * The instance could be promoted for the previous term. But promotion > * has no effect on following terms. > diff --git a/src/lib/raft/raft.h b/src/lib/raft/raft.h > index 817148792..7115f658f 100644 > --- a/src/lib/raft/raft.h > +++ b/src/lib/raft/raft.h > @@ -199,6 +199,10 @@ struct raft { > uint32_t vote; > /** Statistics which node voted for who. */ > struct raft_vote votes[VCLOCK_MAX]; > + /** How many nodes voted in the current term. */ > + int voted_count; > + /** Max vote count given to any node in the current term. */ > + int max_vote_count; > /** Number of votes necessary for successful election. */ > int election_quorum; > /** > ==================== > >>> +static bool >>> +raft_has_split_vote(const struct raft *raft) >>> +{ >>> + int max_vote = 0; >>> + int vote_vac = raft->cluster_size; >>> + int quorum = raft->election_quorum; >>> + for (int i = 0; i < VCLOCK_MAX; ++i) { >>> + int count = raft->votes[i].count; >>> + vote_vac -= count; >>> + if (count > max_vote) >>> + max_vote = count; >>> + } >>> + return max_vote < quorum && max_vote + vote_vac < quorum; >> This is equal to `return max_vote + vote_vac < quorum` > Ouch, that was stupid indeed. I honestly did multiple self-reviews > and still missed it. Don't bother. Could happen to anyone. > ==================== > @@ -175,7 +175,7 @@ raft_has_split_vote(const struct raft *raft) > if (count > max_vote) > max_vote = count; > } > - return max_vote < quorum && max_vote + vote_vac < quorum; > + return max_vote + vote_vac < quorum; > } > ==================== > ... -- Serge Petrenko
next prev parent reply other threads:[~2022-01-20 10:21 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-15 0:48 [Tarantool-patches] [PATCH 0/4] Split vote 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 [this message] 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
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=9a4265d4-cc66-ad1f-5478-ebcc10eef5a8@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=sergepetrenko@tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 3/4] raft: introduce split vote detection' \ /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