From: Serge Petrenko via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>, tarantool-patches@dev.tarantool.org, gorcunov@gmail.com, korablev@tarantool.org Subject: Re: [Tarantool-patches] [PATCH 1/3] vinyl: handle multi-statement recovery txns Date: Fri, 2 Apr 2021 12:24:42 +0300 [thread overview] Message-ID: <54dcea70-8e4f-a91f-d3c5-2ade5e922ff1@tarantool.org> (raw) In-Reply-To: <39bfed3293d262592e646eb4ca6c60f5022eac26.1617315744.git.v.shpilevoy@tarantool.org> 02.04.2021 01:23, Vladislav Shpilevoy пишет: > During recovery and xlog replay vinyl skips the statements already > stored in runs. Indeed, their re-insertion into the mems would > lead to their second dump otherwise. > > But that results into an issue that the recovery transactions in > vinyl don't have a write set - their tx->log is empty. On the > other hand they still are added to the write set (xm->writers). > Probably so as not to have too many checks "skip if in recovery" > all over the code. > > It works fine with single-statement transactions, but would break > on multi-statement transactions. Because the decision whether > need to add to the write set was done based on the tx's log > emptiness. It is always empty, and so the transaction could be > added to the write set twice and corrupt its list-link member. > > The patch makes the decision about being added to the write set > based on emptiness of the list-link member instead of the log so > it works fine both during recovery and normal operation. > > Needed for #5874 Hi! Thanks for the patch! Looks fine at first glance. > --- > src/box/vy_tx.c | 9 ++++++++- > 1 file changed, 8 insertions(+), 1 deletion(-) > > diff --git a/src/box/vy_tx.c b/src/box/vy_tx.c > index ff63cd7a1..cd210beb0 100644 > --- a/src/box/vy_tx.c > +++ b/src/box/vy_tx.c > @@ -899,8 +899,15 @@ vy_tx_begin_statement(struct vy_tx *tx, struct space *space, void **savepoint) > } > assert(tx->state == VINYL_TX_READY); > tx->last_stmt_space = space; > - if (stailq_empty(&tx->log)) > + /* > + * When want to add to the writer list, can't rely on the log emptiness. > + * During recovery it is empty always for the data stored both in runs > + * and xlogs. Must check the list member explicitly. > + */ > + if (rlist_empty(&tx->in_writers)) { > + assert(stailq_empty(&tx->log)); > rlist_add_entry(&tx->xm->writers, tx, in_writers); > + } > *savepoint = stailq_last(&tx->log); > return 0; > } -- Serge Petrenko
next prev parent reply other threads:[~2021-04-02 9:24 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-01 22:23 [Tarantool-patches] [PATCH 0/3] Transactional recovery Vladislav Shpilevoy via Tarantool-patches 2021-04-01 22:23 ` [Tarantool-patches] [PATCH 1/3] vinyl: handle multi-statement recovery txns Vladislav Shpilevoy via Tarantool-patches 2021-04-02 9:24 ` Serge Petrenko via Tarantool-patches [this message] 2021-04-01 22:23 ` [Tarantool-patches] [PATCH 2/3] recovery: make it transactional Vladislav Shpilevoy via Tarantool-patches 2021-04-02 11:47 ` Serge Petrenko via Tarantool-patches 2021-04-03 13:18 ` Vladislav Shpilevoy via Tarantool-patches 2021-04-05 8:36 ` Serge Petrenko via Tarantool-patches 2021-04-02 15:11 ` Cyrill Gorcunov via Tarantool-patches 2021-04-01 22:23 ` [Tarantool-patches] [PATCH 3/3] box: remove is_local_recovery variable Vladislav Shpilevoy via Tarantool-patches 2021-04-02 11:47 ` Serge Petrenko via Tarantool-patches 2021-04-03 13:18 ` Vladislav Shpilevoy via Tarantool-patches 2021-04-05 8:17 ` Serge Petrenko via Tarantool-patches 2021-04-02 9:42 ` [Tarantool-patches] [PATCH 0/3] Transactional recovery Konstantin Osipov via Tarantool-patches 2021-04-05 16:14 ` Kirill Yukhin 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=54dcea70-8e4f-a91f-d3c5-2ade5e922ff1@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=gorcunov@gmail.com \ --cc=korablev@tarantool.org \ --cc=sergepetrenko@tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 1/3] vinyl: handle multi-statement recovery txns' \ /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