From: Serge Petrenko via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: v.shpilevoy@tarantool.org, gorcunov@gmail.com
Cc: tarantool-patches@dev.tarantool.org
Subject: [Tarantool-patches] [PATCH v2 2/7] applier: extract tx boundary checks from applier_read_tx into a separate routine
Date: Wed, 24 Mar 2021 15:24:12 +0300 [thread overview]
Message-ID: <31d242da3f691029c6fc670c902290a77fe36ae1.1616588119.git.sergepetrenko@tarantool.org> (raw)
In-Reply-To: <cover.1616588119.git.sergepetrenko@tarantool.org>
Introduce a new routine, set_next_tx_row(), which checks tx boundary
violation and appends the new row to the current tx in case everything
is ok.
set_next_tx_row() is extracted from applier_read_tx() because it's a
common part of transaction assembly both for recovery and applier.
The only difference for recovery will be that the routine which's
responsible for tx assembly won't read rows. It'll be a callback ran on
each new row being read from WAL.
Prerequisite #5874
Part-of #5566
---
src/box/applier.cc | 117 +++++++++++++++++++++++----------------------
1 file changed, 60 insertions(+), 57 deletions(-)
diff --git a/src/box/applier.cc b/src/box/applier.cc
index 326cf18d2..65afa5e98 100644
--- a/src/box/applier.cc
+++ b/src/box/applier.cc
@@ -657,6 +657,64 @@ applier_read_tx_row(struct applier *applier)
return tx_row;
}
+static inline int64_t
+set_next_tx_row(struct stailq *rows, struct applier_tx_row *tx_row, int64_t tsn)
+{
+ struct xrow_header *row = &tx_row->row;
+
+ if (iproto_type_is_error(row->type))
+ xrow_decode_error_xc(row);
+
+ /* Replication request. */
+ if (row->replica_id >= VCLOCK_MAX) {
+ /*
+ * A safety net, this can only occur if we're fed a strangely
+ * broken xlog. row->replica_id == 0, when reading heartbeats
+ * from an anonymous instance.
+ */
+ tnt_raise(ClientError, ER_UNKNOWN_REPLICA,
+ int2str(row->replica_id),
+ tt_uuid_str(&REPLICASET_UUID));
+ }
+ if (tsn == 0) {
+ /*
+ * Transaction id must be derived from the log sequence number
+ * of the first row in the transaction.
+ */
+ tsn = row->tsn;
+ if (row->lsn != tsn)
+ tnt_raise(ClientError, ER_PROTOCOL,
+ "Transaction id must be equal to LSN of the "
+ "first row in the transaction.");
+ } else if (tsn != row->tsn) {
+ tnt_raise(ClientError, ER_UNSUPPORTED, "replication",
+ "interleaving transactions");
+ }
+
+ assert(row->bodycnt <= 1);
+ if (row->is_commit) {
+ /* Signal the caller that we've reached the tx end. */
+ tsn = 0;
+ } else if (row->bodycnt == 1) {
+ /*
+ * Save row body to gc region. Not done for single-statement
+ * transactions and the last row of multi-statement transactions
+ * knowing that the input buffer will not be used while the
+ * transaction is applied.
+ */
+ void *new_base = region_alloc(&fiber()->gc, row->body->iov_len);
+ if (new_base == NULL)
+ tnt_raise(OutOfMemory, row->body->iov_len, "region",
+ "xrow body");
+ memcpy(new_base, row->body->iov_base, row->body->iov_len);
+ /* Adjust row body pointers. */
+ row->body->iov_base = new_base;
+ }
+
+ stailq_add_tail(rows, &tx_row->next);
+ return tsn;
+}
+
/**
* Read one transaction from network using applier's input buffer.
* Transaction rows are placed onto fiber gc region.
@@ -672,63 +730,8 @@ applier_read_tx(struct applier *applier, struct stailq *rows)
stailq_create(rows);
do {
struct applier_tx_row *tx_row = applier_read_tx_row(applier);
- struct xrow_header *row = &tx_row->row;
-
- if (iproto_type_is_error(row->type))
- xrow_decode_error_xc(row);
-
- /* Replication request. */
- if (row->replica_id >= VCLOCK_MAX) {
- /*
- * A safety net, this can only occur
- * if we're fed a strangely broken xlog.
- * row->replica_id == 0, when reading
- * heartbeats from an anonymous instance.
- */
- tnt_raise(ClientError, ER_UNKNOWN_REPLICA,
- int2str(row->replica_id),
- tt_uuid_str(&REPLICASET_UUID));
- }
- if (tsn == 0) {
- /*
- * Transaction id must be derived from the log sequence
- * number of the first row in the transaction.
- */
- tsn = row->tsn;
- if (row->lsn != tsn)
- tnt_raise(ClientError, ER_PROTOCOL,
- "Transaction id must be equal to "
- "LSN of the first row in the "
- "transaction.");
- }
- if (tsn != row->tsn)
- tnt_raise(ClientError, ER_UNSUPPORTED,
- "replication",
- "interleaving transactions");
-
- assert(row->bodycnt <= 1);
- if (row->bodycnt == 1 && !row->is_commit) {
- /*
- * Save row body to gc region.
- * Not done for single-statement
- * transactions knowing that the input
- * buffer will not be used while the
- * transaction is applied.
- */
- void *new_base = region_alloc(&fiber()->gc,
- row->body->iov_len);
- if (new_base == NULL)
- tnt_raise(OutOfMemory, row->body->iov_len,
- "region", "xrow body");
- memcpy(new_base, row->body->iov_base,
- row->body->iov_len);
- /* Adjust row body pointers. */
- row->body->iov_base = new_base;
- }
- stailq_add_tail(rows, &tx_row->next);
-
- } while (!stailq_last_entry(rows, struct applier_tx_row,
- next)->row.is_commit);
+ tsn = set_next_tx_row(rows, tx_row, tsn);
+ } while (tsn != 0);
}
static void
--
2.24.3 (Apple Git-128)
next prev parent reply other threads:[~2021-03-24 12:25 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 ` Serge Petrenko via Tarantool-patches [this message]
2021-03-26 12:35 ` [Tarantool-patches] [PATCH v2 2/7] applier: extract tx boundary checks from applier_read_tx into a separate routine 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
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=31d242da3f691029c6fc670c902290a77fe36ae1.1616588119.git.sergepetrenko@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 2/7] applier: extract tx boundary checks from applier_read_tx into a separate routine' \
/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