From: Cyrill Gorcunov via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> Cc: tml <tarantool-patches@dev.tarantool.org> Subject: Re: [Tarantool-patches] [PATCH] limbo: introduce request processing hooks Date: Mon, 12 Jul 2021 11:09:44 +0300 [thread overview] Message-ID: <YOv4yNnQVLgLHrkr@grain> (raw) In-Reply-To: <4965b115-dd42-0129-0086-a0ff711fa648@tarantool.org> On Mon, Jul 12, 2021 at 10:03:32AM +0200, Vladislav Shpilevoy wrote: > > > > Now imagine the following: we validated the incoming packet and > > remember its term in promote_term_map, then we start writting > > this packet into our WAL and write procedure failed. > > That is the core problem of your entire approach - why do you imagine > we update promote_term_map before writing to WAL? We do not do that. We don't do that now, and this is all this patch about - we must not write the PROMOTE from split-brained node into our wal file at all, for exactly this reason I splitted processing into phases: "filter" and "application". > And you should not do that. Before WAL write there should no be any > changes. **Zero changes before WAL write**. Before you write to WAL, > you can only validate requests. Using `const struct txn_limbo *`. With > zero changes. If we write screwed PROMOTEs request into our WAL then this patch is not needed at all.
next prev parent reply other threads:[~2021-07-12 8:09 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-10 22:28 Cyrill Gorcunov via Tarantool-patches 2021-07-11 14:00 ` Vladislav Shpilevoy via Tarantool-patches 2021-07-11 18:22 ` Cyrill Gorcunov via Tarantool-patches 2021-07-12 8:03 ` Vladislav Shpilevoy via Tarantool-patches 2021-07-12 8:09 ` Cyrill Gorcunov via Tarantool-patches [this message] 2021-07-12 21:20 ` Vladislav Shpilevoy via Tarantool-patches 2021-07-12 22:32 ` Cyrill Gorcunov via Tarantool-patches 2021-07-13 19:32 ` Vladislav Shpilevoy via Tarantool-patches 2021-07-12 8:01 ` Serge Petrenko via Tarantool-patches 2021-07-12 8:04 ` Vladislav Shpilevoy via Tarantool-patches 2021-07-12 8:12 ` Cyrill Gorcunov via Tarantool-patches 2021-07-12 8:23 ` Cyrill Gorcunov via Tarantool-patches 2021-07-12 21:20 ` Vladislav Shpilevoy via Tarantool-patches 2021-07-12 22:34 ` Cyrill Gorcunov via Tarantool-patches 2021-07-12 9:43 ` Cyrill Gorcunov via Tarantool-patches 2021-07-12 15:48 ` Cyrill Gorcunov via Tarantool-patches 2021-07-12 16:49 ` Serge Petrenko via Tarantool-patches 2021-07-12 17:04 ` Cyrill Gorcunov via Tarantool-patches 2021-07-12 21:20 ` Vladislav Shpilevoy via Tarantool-patches 2021-07-12 21:52 ` Cyrill Gorcunov via Tarantool-patches 2021-07-12 7:54 ` Serge Petrenko 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=YOv4yNnQVLgLHrkr@grain \ --to=tarantool-patches@dev.tarantool.org \ --cc=gorcunov@gmail.com \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH] limbo: introduce request processing hooks' \ /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