From: Serge Petrenko <sergepetrenko@tarantool.org> To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>, Leonid Vasiliev <lvasiliev@tarantool.org>, sergos@tarantool.org, gorcunov@gmail.com Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH 3/8] txn: add TXN_WAIT_ACK flag Date: Mon, 22 Jun 2020 12:44:04 +0300 [thread overview] Message-ID: <9c56561d-554c-d6a9-3bf8-c942ee528073@tarantool.org> (raw) In-Reply-To: <409bc44b-2b6b-1d49-f8c7-82f979480b2f@tarantool.org> 21.06.2020 19:25, Vladislav Shpilevoy пишет: > Thanks for the review! > >>> stailq_foreach_entry(stmt, &txn->stmts, next) { >>> if (stmt->has_triggers) { >>> txn_init_triggers(txn); >>> rlist_splice(&txn->on_commit, &stmt->on_commit); >>> } >>> + is_sync = is_sync || stmt->space->def->opts.is_sync; >> Seems like >> "... || (stmt->space != NULL && stmt->space->def->opts.is_sync);" >> can be moved here from "replication: make sync transactions wait quorum". >> >> LGTM. > I don't think it is a good idea. At this commit stmt->space can't be > NULL. This becomes possible only after Sergey P. starts using txns > to write confirm and rollback entries, which don't relate to any > space. Actually, stmt->space is NULL for NOPs. > > However I changed this place - I moved is_sync calculation after > stmt->row == NULL check. So as a read from a sync space wouldn't > turn the transaction into a synchronous one: > > ==================== > commit e29fd482e0954913b87776d0a83ba04ef14683d8 > Author: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> > Date: Sun Jun 21 18:12:53 2020 +0200 > > txn: don't do sync flag calculation for read statements > > [TO BE SQUASHED INTO THE PREVIOUS COMMIT] > > diff --git a/src/box/txn.c b/src/box/txn.c > index b50e7c1f8..22591a365 100644 > --- a/src/box/txn.c > +++ b/src/box/txn.c > @@ -502,12 +502,13 @@ txn_journal_entry_new(struct txn *txn) > txn_init_triggers(txn); > rlist_splice(&txn->on_commit, &stmt->on_commit); > } > - is_sync = is_sync || stmt->space->def->opts.is_sync; > > /* A read (e.g. select) request */ > if (stmt->row == NULL) > continue; > > + is_sync = is_sync || stmt->space->def->opts.is_sync; > + > if (stmt->row->replica_id == 0) > *local_row++ = stmt->row; > else > -- Serge Petrenko
next prev parent reply other threads:[~2020-06-22 9:44 UTC|newest] Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-09 12:20 [Tarantool-patches] [PATCH 0/8] wait for lsn and confirm Serge Petrenko 2020-06-09 12:20 ` [Tarantool-patches] [PATCH 1/8] replication: introduce space.is_sync option Serge Petrenko 2020-06-10 23:51 ` Vladislav Shpilevoy 2020-06-18 22:27 ` Leonid Vasiliev 2020-06-21 16:24 ` Vladislav Shpilevoy 2020-06-09 12:20 ` [Tarantool-patches] [PATCH 2/8] replication: introduce replication_sync_quorum cfg Serge Petrenko 2020-06-10 23:51 ` Vladislav Shpilevoy 2020-06-15 23:05 ` Vladislav Shpilevoy 2020-06-18 22:54 ` Leonid Vasiliev 2020-06-19 17:45 ` Serge Petrenko 2020-06-21 16:25 ` Vladislav Shpilevoy 2020-06-09 12:20 ` [Tarantool-patches] [PATCH 3/8] txn: add TXN_WAIT_ACK flag Serge Petrenko 2020-06-18 23:12 ` Leonid Vasiliev 2020-06-21 16:25 ` Vladislav Shpilevoy 2020-06-22 9:44 ` Serge Petrenko [this message] 2020-06-23 22:13 ` Vladislav Shpilevoy 2020-06-09 12:20 ` [Tarantool-patches] [PATCH 4/8] replication: make sync transactions wait quorum Serge Petrenko 2020-06-10 23:51 ` Vladislav Shpilevoy 2020-06-11 14:57 ` Vladislav Shpilevoy 2020-06-15 23:05 ` Vladislav Shpilevoy 2020-06-19 12:39 ` Leonid Vasiliev 2020-06-25 21:48 ` Vladislav Shpilevoy 2020-06-09 12:20 ` [Tarantool-patches] [PATCH 5/8] txn_limbo: follow-up fixes Serge Petrenko 2020-06-10 23:51 ` Vladislav Shpilevoy 2020-06-11 8:46 ` Serge Petrenko 2020-06-11 13:01 ` Vladislav Shpilevoy 2020-06-09 12:20 ` [Tarantool-patches] [PATCH 6/8] txn_limbo: fix instance id assignment Serge Petrenko 2020-06-10 23:51 ` Vladislav Shpilevoy 2020-06-09 12:20 ` [Tarantool-patches] [PATCH 7/8] xrow: introduce CONFIRM entry Serge Petrenko 2020-06-19 15:18 ` Leonid Vasiliev 2020-06-22 10:14 ` Serge Petrenko 2020-06-23 8:33 ` Serge Petrenko 2020-06-09 12:20 ` [Tarantool-patches] [PATCH 8/8] replication: write and read CONFIRM entries Serge Petrenko 2020-06-10 23:51 ` Vladislav Shpilevoy 2020-06-11 8:56 ` Serge Petrenko 2020-06-11 13:04 ` Vladislav Shpilevoy 2020-06-11 14:57 ` Vladislav Shpilevoy 2020-06-15 23:05 ` Vladislav Shpilevoy 2020-06-18 11:32 ` Leonid Vasiliev 2020-06-18 21:49 ` Vladislav Shpilevoy 2020-06-19 17:48 ` Serge Petrenko 2020-06-19 17:50 ` Serge Petrenko 2020-06-23 8:35 ` Serge Petrenko 2020-06-20 15:06 ` Leonid Vasiliev 2020-06-22 10:34 ` Serge Petrenko 2020-06-23 8:34 ` Serge Petrenko 2020-06-25 22:04 ` Vladislav Shpilevoy 2020-06-25 22:31 ` Vladislav Shpilevoy 2020-06-26 10:58 ` Serge Petrenko 2020-06-09 12:53 ` [Tarantool-patches] [PATCH 0/2] A few fixes for building Cyrill Gorcunov 2020-06-09 12:53 ` [Tarantool-patches] [PATCH 1/2] box/applier: fix typo Cyrill Gorcunov 2020-06-10 9:18 ` Sergey Ostanevich 2020-06-09 12:53 ` [Tarantool-patches] [PATCH 2/2] box: use tnt_raise for quorum check Cyrill Gorcunov 2020-06-10 9:17 ` Sergey Ostanevich 2020-06-10 10:45 ` Serge Petrenko 2020-06-22 21:51 ` [Tarantool-patches] [PATCH 0/8] wait for lsn and confirm 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=9c56561d-554c-d6a9-3bf8-c942ee528073@tarantool.org \ --to=sergepetrenko@tarantool.org \ --cc=gorcunov@gmail.com \ --cc=lvasiliev@tarantool.org \ --cc=sergos@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 3/8] txn: add TXN_WAIT_ACK flag' \ /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