From: Vladislav Shpilevoy via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Serge Petrenko <sergepetrenko@tarantool.org>, gorcunov@gmail.com Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH v2 5/7] applier: make final join transactional Date: Fri, 26 Mar 2021 21:49:08 +0100 [thread overview] Message-ID: <e9cfe94d-7e47-b7e5-d85b-21f06af58322@tarantool.org> (raw) In-Reply-To: <5cfa8f8e4d733aabd53138dd3ffc6f524ffac743.1616588119.git.sergepetrenko@tarantool.org> I appreciate the work you did here! See 3 comments below. On 24.03.2021 13:24, Serge Petrenko wrote: > Now applier assembles rows into transactions not only on subscribe > stage, but also during final join / register. > > This was necessary for correct handling of rolled back synchronous > transactions in final join stream. > > Part of #5566 > --- > src/box/applier.cc | 126 ++++++++++++++++++++++----------------------- > 1 file changed, 61 insertions(+), 65 deletions(-) > > diff --git a/src/box/applier.cc b/src/box/applier.cc > index d53f13711..9a8b0f0fc 100644 > --- a/src/box/applier.cc > +++ b/src/box/applier.cc > @@ -524,27 +509,19 @@ applier_wait_register(struct applier *applier, uint64_t row_count) > * Receive final data. > */ > while (true) { > - coio_read_xrow(coio, ibuf, &row); > - applier->last_row_time = ev_monotonic_now(loop()); > - if (iproto_type_is_dml(row.type)) { > - vclock_follow_xrow(&replicaset.vclock, &row); > - if (apply_final_join_row(&row) != 0) > - diag_raise(); > - if (++row_count % 100000 == 0) > - say_info("%.1fM rows received", row_count / 1e6); > - } else if (row.type == IPROTO_OK) { > - /* > - * Current vclock. This is not used now, > - * ignore. > - */ 1. The comment was helpful, lets keep it. > - ++row_count; > - break; /* end of stream */ > - } else if (iproto_type_is_error(row.type)) { > - xrow_decode_error_xc(&row); /* rethrow error */ > - } else { > - tnt_raise(ClientError, ER_UNKNOWN_REQUEST_TYPE, > - (uint32_t) row.type); > + struct stailq rows; > + applier_read_tx(applier, &rows, &row_count); > + struct xrow_header *first_row = > + &stailq_first_entry(&rows, struct applier_tx_row, > + next)->row; > + if (first_row->type == IPROTO_OK) { > + assert(first_row == > + &stailq_last_entry(&rows, struct applier_tx_row, > + next)->row); > + break; > } > + if (apply_final_join_tx(&rows) != 0) > + diag_raise(); > } > > return row_count; > @@ -646,8 +613,11 @@ applier_read_tx_row(struct applier *applier) > * messages so we can't assume that if we haven't heard > * from the master for quite a while the connection is > * broken - the master might just be idle. > + * Also there are no timeouts during final join and register. > */ > - if (applier->version_id < version_id(1, 7, 7)) > + if (applier->version_id < version_id(1, 7, 7) || > + applier->state == APPLIER_FINAL_JOIN || > + applier->state == APPLIER_REGISTER) 2. Maybe it would be better to pass the timeout from the upper level and always use coio_read_xrow_timeout_xc(). For the mentioned conditions it would be infinity. Anyway the non-timed version in the end uses TIMEOUT_INFINITY too (coio_read_ahead). That way it would be less tricky conditions checks in the generic code. > coio_read_xrow(coio, ibuf, row); > else > coio_read_xrow_timeout_xc(coio, ibuf, row, timeout); > @@ -731,6 +702,9 @@ applier_read_tx(struct applier *applier, struct stailq *rows) > do { > struct applier_tx_row *tx_row = applier_read_tx_row(applier); > tsn = set_next_tx_row(rows, tx_row, tsn); > + > + if (row_count != NULL && ++*row_count % 100000 == 0) > + say_info("%.1fM rows received", *row_count / 1e6); 3. Hm. That adds branching and heavy '%' operation. Maybe you could make it return number of rows and in the caller code do this check + log. So it would affect only the joins. > @@ -1254,7 +1250,7 @@ applier_subscribe(struct applier *applier) > } > > struct stailq rows; > - applier_read_tx(applier, &rows); > + applier_read_tx(applier, &rows, NULL); > > /* > * In case of an heartbeat message wake a writer up >
next prev parent reply other threads:[~2021-03-26 20:49 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-24 12:24 [Tarantool-patches] [PATCH v2 0/7] applier: handle synchronous transactions during final Serge Petrenko via Tarantool-patches 2021-03-24 12:24 ` [Tarantool-patches] [PATCH v2 1/7] replication: fix a hang on final join retry Serge Petrenko via Tarantool-patches 2021-03-26 20:44 ` Vladislav Shpilevoy via Tarantool-patches 2021-03-27 16:52 ` Serge Petrenko via Tarantool-patches 2021-03-29 21:50 ` Vladislav Shpilevoy via Tarantool-patches 2021-03-24 12:24 ` [Tarantool-patches] [PATCH v2 2/7] applier: extract tx boundary checks from applier_read_tx into a separate routine Serge Petrenko via Tarantool-patches 2021-03-26 12:35 ` Cyrill Gorcunov via Tarantool-patches 2021-03-27 16:54 ` Serge Petrenko via Tarantool-patches 2021-03-24 12:24 ` [Tarantool-patches] [PATCH v2 3/7] applier: extract plain tx application from applier_apply_tx() Serge Petrenko via Tarantool-patches 2021-03-26 20:47 ` Vladislav Shpilevoy via Tarantool-patches 2021-03-27 17:34 ` Serge Petrenko via Tarantool-patches 2021-03-27 18:30 ` [Tarantool-patches] [PATCH v2 3.5/7] applier: fix not releasing the latch on apply_synchro_row() fail Serge Petrenko via Tarantool-patches 2021-03-29 21:50 ` Vladislav Shpilevoy via Tarantool-patches 2021-03-30 8:15 ` Serge Petrenko via Tarantool-patches 2021-03-24 12:24 ` [Tarantool-patches] [PATCH v2 4/7] applier: remove excess last_row_time update from subscribe loop Serge Petrenko via Tarantool-patches 2021-03-24 12:24 ` [Tarantool-patches] [PATCH v2 5/7] applier: make final join transactional Serge Petrenko via Tarantool-patches 2021-03-26 20:49 ` Vladislav Shpilevoy via Tarantool-patches [this message] 2021-03-27 19:05 ` Serge Petrenko via Tarantool-patches 2021-03-29 21:51 ` Vladislav Shpilevoy via Tarantool-patches 2021-03-30 8:15 ` Serge Petrenko via Tarantool-patches 2021-03-24 12:24 ` [Tarantool-patches] [PATCH v2 6/7] replication: tolerate synchro rollback during final join Serge Petrenko via Tarantool-patches 2021-03-24 12:45 ` Serge Petrenko via Tarantool-patches 2021-03-26 20:49 ` Vladislav Shpilevoy via Tarantool-patches 2021-03-27 19:23 ` Serge Petrenko via Tarantool-patches 2021-03-24 12:24 ` [Tarantool-patches] [PATCH v2 7/7] replication: do not ignore replica vclock on register Serge Petrenko via Tarantool-patches 2021-03-26 20:50 ` Vladislav Shpilevoy via Tarantool-patches 2021-03-27 20:13 ` Serge Petrenko via Tarantool-patches 2021-03-29 21:51 ` Vladislav Shpilevoy via Tarantool-patches 2021-03-30 8:16 ` Serge Petrenko via Tarantool-patches 2021-03-30 12:33 ` Serge Petrenko via Tarantool-patches 2021-03-26 13:46 ` [Tarantool-patches] [PATCH v2 0/7] applier: handle synchronous transactions during final Cyrill Gorcunov via Tarantool-patches 2021-03-30 20:13 ` Vladislav Shpilevoy via Tarantool-patches 2021-04-05 16:15 ` 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=e9cfe94d-7e47-b7e5-d85b-21f06af58322@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=gorcunov@gmail.com \ --cc=sergepetrenko@tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v2 5/7] applier: make final join transactional' \ /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