From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: tarantool-patches@dev.tarantool.org, sergepetrenko@tarantool.org, gorcunov@gmail.com Subject: Re: [Tarantool-patches] [PATCH v2 09/11] raft: introduce state machine Date: Sat, 19 Sep 2020 17:50:31 +0200 [thread overview] Message-ID: <3e56d915-2078-1181-ae6c-1ee1743e0e1c@tarantool.org> (raw) In-Reply-To: <f87ff590-60b0-89f5-becc-38d89885de76@tarantool.org> And my new changes on top of it, in a separate commit. ==================== diff --git a/src/box/applier.cc b/src/box/applier.cc index c352faf5e..10186ab91 100644 --- a/src/box/applier.cc +++ b/src/box/applier.cc @@ -885,6 +885,11 @@ static int applier_handle_raft(struct applier *applier, struct xrow_header *row) { assert(iproto_type_is_raft_request(row->type)); + if (applier->instance_id == 0) { + diag_set(ClientError, ER_PROTOCOL, "Can't apply a Raft request " + "from an instance without an ID"); + return -1; + } struct raft_request req; struct vclock candidate_clock; diff --git a/src/box/raft.c b/src/box/raft.c index 07a49351f..b3ab94bd7 100644 --- a/src/box/raft.c +++ b/src/box/raft.c @@ -347,6 +347,7 @@ raft_process_msg(const struct raft_request *req, uint32_t source) if (req->vote != 0) { switch (raft.state) { case RAFT_STATE_FOLLOWER: + case RAFT_STATE_LEADER: /* * Can't respond on vote requests when Raft is disabled. */ @@ -386,6 +387,12 @@ raft_process_msg(const struct raft_request *req, uint32_t source) "indirect votes are not allowed"); break; } + if (raft.leader != 0) { + say_info("RAFT: vote request is skipped - the " + "leader is already known - %u", + raft.leader); + break; + } /* * Either the term is new, or didn't vote in the current * term yet. Anyway can vote now. @@ -415,16 +422,6 @@ raft_process_msg(const struct raft_request *req, uint32_t source) } raft_sm_become_leader(); break; - case RAFT_STATE_LEADER: - /* - * If the node is still a leader, it ignores all votes. - * Indeed, if the received vote would be from a new - * term, the node would bump its own term and would - * enter the follower state by now. If the vote is from - * the current term, then the leader can freely ignore - * it. - */ - break; default: unreachable(); } @@ -466,6 +463,12 @@ end: void raft_process_heartbeat(uint32_t source) { + /* + * Raft handles heartbeats from all instances, including anon instances + * which don't participate in Raft. + */ + if (source == 0) + return; /* * When not a candidate - don't wait for anything. Therefore do not care * about the leader being dead. @@ -746,6 +749,7 @@ raft_sm_schedule_new_vote(uint32_t new_vote) { say_info("RAFT: vote for %u, follow", new_vote, raft.volatile_term); assert(raft.volatile_vote == 0); + assert(raft.leader == 0); assert(raft.state == RAFT_STATE_FOLLOWER); raft.volatile_vote = new_vote; raft_sm_pause_and_dump(); @@ -929,15 +933,8 @@ raft_cfg_election_quorum(void) return; if (raft.vote_count < raft_election_quorum()) return; - /* - * The node is a candidate. It means its state if fully synced with - * disk. Otherwise it would be a follower. - */ - assert(!raft.is_write_in_progress); - raft.state = RAFT_STATE_LEADER; - raft.leader = instance_id; + raft_sm_become_leader(); raft_broadcast_new_state(); - box_update_ro_summary(); } void
next prev parent reply other threads:[~2020-09-19 15:50 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-09 23:16 [Tarantool-patches] [PATCH v2 00/11] dRaft Vladislav Shpilevoy 2020-09-09 23:16 ` [Tarantool-patches] [PATCH v2 01/11] applier: store instance_id in struct applier Vladislav Shpilevoy 2020-09-14 9:38 ` Serge Petrenko 2020-09-19 15:44 ` Vladislav Shpilevoy 2020-09-21 6:23 ` Serge Petrenko 2020-09-09 23:16 ` [Tarantool-patches] [PATCH v2 10/11] raft: introduce box.info.raft Vladislav Shpilevoy 2020-09-14 9:42 ` Serge Petrenko 2020-09-09 23:16 ` [Tarantool-patches] [PATCH v2 11/11] [tosquash] raft: a swarm of minor fixes Vladislav Shpilevoy 2020-09-14 10:13 ` Serge Petrenko 2020-09-09 23:16 ` [Tarantool-patches] [PATCH v2 02/11] box: introduce summary RO flag Vladislav Shpilevoy 2020-09-09 23:16 ` [Tarantool-patches] [PATCH v2 03/11] wal: don't touch box.cfg.wal_dir more than once Vladislav Shpilevoy 2020-09-09 23:16 ` [Tarantool-patches] [PATCH v2 04/11] replication: track registered replica count Vladislav Shpilevoy 2020-09-09 23:16 ` [Tarantool-patches] [PATCH v2 05/11] [wip] box: do not register outgoing connections Vladislav Shpilevoy 2020-09-09 23:16 ` [Tarantool-patches] [PATCH v2 06/11] raft: introduce persistent raft state Vladislav Shpilevoy 2020-09-09 23:16 ` [Tarantool-patches] [PATCH v2 07/11] raft: introduce box.cfg.raft_* options Vladislav Shpilevoy 2020-09-09 23:16 ` [Tarantool-patches] [PATCH v2 08/11] raft: relay status updates to followers Vladislav Shpilevoy 2020-09-20 17:17 ` Vladislav Shpilevoy 2020-09-21 7:13 ` Serge Petrenko 2020-09-21 10:50 ` Serge Petrenko 2020-09-21 22:47 ` Vladislav Shpilevoy 2020-09-22 8:48 ` Serge Petrenko 2020-09-21 22:47 ` Vladislav Shpilevoy 2020-09-22 8:47 ` Serge Petrenko 2020-09-09 23:17 ` [Tarantool-patches] [PATCH v2 09/11] raft: introduce state machine Vladislav Shpilevoy 2020-09-19 15:49 ` Vladislav Shpilevoy 2020-09-19 15:50 ` Vladislav Shpilevoy [this message] 2020-09-21 8:20 ` Serge Petrenko 2020-09-21 8:22 ` Serge Petrenko 2020-09-21 8:34 ` Serge Petrenko 2020-09-21 22:47 ` Vladislav Shpilevoy 2020-09-22 8:49 ` Serge Petrenko 2020-09-22 22:48 ` Vladislav Shpilevoy 2020-09-23 9:59 ` Serge Petrenko 2020-09-23 20:31 ` Vladislav Shpilevoy 2020-09-24 9:34 ` Serge Petrenko 2020-09-19 15:58 ` [Tarantool-patches] [PATCH v2 12/11] dRaft Vladislav Shpilevoy 2020-09-19 15:59 ` Vladislav Shpilevoy 2020-09-21 7:24 ` Serge Petrenko 2020-09-21 22:48 ` [Tarantool-patches] [PATCH v2 12/11] raft: add tests Vladislav Shpilevoy 2020-09-30 10:56 ` [Tarantool-patches] [PATCH v2 00/11] dRaft Kirill Yukhin
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=3e56d915-2078-1181-ae6c-1ee1743e0e1c@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=gorcunov@gmail.com \ --cc=sergepetrenko@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v2 09/11] raft: introduce state machine' \ /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