From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: tarantool-patches@dev.tarantool.org, sergepetrenko@tarantool.org Subject: [Tarantool-patches] [PATCH 2/6] raft: factor out the code to wakeup worker fiber Date: Wed, 14 Oct 2020 01:28:28 +0200 [thread overview] Message-ID: <f903a2b8f33583e7567e4f374da241e1c2cfe77b.1602631481.git.v.shpilevoy@tarantool.org> (raw) In-Reply-To: <cover.1602631481.git.v.shpilevoy@tarantool.org> Raft has a worker fiber to perform async tasks such as WAL write, state broadcast. The worker was created and woken up from 2 places, leading at least to code duplication. The patch wraps it into a new function raft_worker_wakeup(), and uses it. The patch is not need for anything functional, but was created while working on #5339 and trying ideas. The patch seems to be good refactoring making the code simpler, and therefore it is submitted. --- src/box/raft.c | 34 +++++++++++++++++++++++----------- 1 file changed, 23 insertions(+), 11 deletions(-) diff --git a/src/box/raft.c b/src/box/raft.c index 0b6c373e8..f51e87fde 100644 --- a/src/box/raft.c +++ b/src/box/raft.c @@ -178,6 +178,13 @@ raft_election_quorum(void) return MIN(replication_synchro_quorum, replicaset.registered_count); } +/** + * Wakeup the Raft worker fiber in order to do some async work. If the fiber + * does not exist yet, it is created. + */ +static void +raft_worker_wakeup(void); + /** Schedule broadcast of the complete Raft state to all the followers. */ static void raft_schedule_broadcast(void); @@ -670,10 +677,8 @@ raft_sm_pause_and_dump(void) if (raft.is_write_in_progress) return; ev_timer_stop(loop(), &raft.timer); + raft_worker_wakeup(); raft.is_write_in_progress = true; - if (raft.worker == NULL) - raft.worker = fiber_new("raft_worker", raft_worker_f); - fiber_wakeup(raft.worker); } static void @@ -988,21 +993,28 @@ raft_new_term(void) } static void -raft_schedule_broadcast(void) +raft_worker_wakeup(void) { - raft.is_broadcast_scheduled = true; + if (raft.worker == NULL) { + raft.worker = fiber_new("raft_worker", raft_worker_f); + fiber_set_joinable(raft.worker, true); + } /* * Don't wake the fiber if it writes something. Otherwise it would be a - * spurious wakeup breaking the WAL write not adapted to this. + * spurious wakeup breaking the WAL write not adapted to this. Also + * don't wakeup the current fiber - it leads to undefined behaviour. */ - if (raft.is_write_in_progress) - return; - if (raft.worker == NULL) - raft.worker = fiber_new("raft_worker", raft_worker_f); - if (raft.worker != fiber()) + if (!raft.is_write_in_progress && fiber() != raft.worker) fiber_wakeup(raft.worker); } +static void +raft_schedule_broadcast(void) +{ + raft.is_broadcast_scheduled = true; + raft_worker_wakeup(); +} + void raft_init(void) { -- 2.21.1 (Apple Git-122.3)
next prev parent reply other threads:[~2020-10-13 23:28 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-13 23:28 [Tarantool-patches] [PATCH 0/6] Raft auto-commit Vladislav Shpilevoy 2020-10-13 23:28 ` [Tarantool-patches] [PATCH 1/6] test: add '_stress' suffix to election_qsync test Vladislav Shpilevoy 2020-10-13 23:28 ` Vladislav Shpilevoy [this message] 2020-10-14 13:29 ` [Tarantool-patches] [PATCH 2/6] raft: factor out the code to wakeup worker fiber Cyrill Gorcunov 2020-10-14 22:40 ` Vladislav Shpilevoy 2020-10-15 6:50 ` Cyrill Gorcunov 2020-10-13 23:28 ` [Tarantool-patches] [PATCH 3/6] raft: new candidate should wait for leader death Vladislav Shpilevoy 2020-10-13 23:28 ` [Tarantool-patches] [PATCH 4/6] raft: introduce on_update trigger Vladislav Shpilevoy 2020-10-13 23:28 ` [Tarantool-patches] [PATCH 5/6] raft: auto-commit transactions of the old leader Vladislav Shpilevoy 2020-10-13 23:28 ` [Tarantool-patches] [PATCH 6/6] qsync: reset confirmed lsn in limbo on owner change Vladislav Shpilevoy 2020-11-24 23:23 ` Vladislav Shpilevoy 2020-10-14 7:34 ` [Tarantool-patches] [PATCH 0/6] Raft auto-commit Serge Petrenko 2020-10-14 22:40 ` Vladislav Shpilevoy
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=f903a2b8f33583e7567e4f374da241e1c2cfe77b.1602631481.git.v.shpilevoy@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=sergepetrenko@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 2/6] raft: factor out the code to wakeup worker fiber' \ /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