From: Serge Petrenko <sergepetrenko@tarantool.org>
To: gorcunov@gmail.com, v.shpilevoy@tarantool.org
Cc: tarantool-patches@dev.tarantool.org
Subject: [Tarantool-patches] [PATCH v3 0/2] fix replication tx boundaries after local space rework
Date: Thu, 2 Jul 2020 16:39:49 +0300 [thread overview]
Message-ID: <cover.1593696889.git.sergepetrenko@tarantool.org> (raw)
https://github.com/tarantool/tarantool/issues/4928
https://github.com/tarantool/tarantool/tree/sp/gh-4928-tx-boundary-fix-nop
Changes in v3:
- Instead of reordering rows in WAL, append
a dummy NOP row to the tx end when needed.
Serge Petrenko (2):
wal: fix tx boundaries
replication: append NOP as the last tx row
src/box/txn.c | 23 ++-
src/box/wal.c | 27 +++-
test/replication/gh-4928-tx-boundaries.result | 138 ++++++++++++++++++
.../gh-4928-tx-boundaries.test.lua | 61 ++++++++
test/replication/suite.cfg | 1 +
5 files changed, 245 insertions(+), 5 deletions(-)
create mode 100644 test/replication/gh-4928-tx-boundaries.result
create mode 100644 test/replication/gh-4928-tx-boundaries.test.lua
--
2.24.3 (Apple Git-128)
next reply other threads:[~2020-07-02 13:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 13:39 Serge Petrenko [this message]
2020-07-02 13:39 ` [Tarantool-patches] [PATCH v3 1/2] wal: fix tx boundaries Serge Petrenko
2020-07-02 13:39 ` [Tarantool-patches] [PATCH v3 2/2] replication: append NOP as the last tx row Serge Petrenko
2020-07-02 14:35 ` Cyrill Gorcunov
2020-07-02 14:49 ` Cyrill Gorcunov
2020-07-02 15:37 ` Cyrill Gorcunov
2020-07-02 20:30 ` Vladislav Shpilevoy
2020-07-03 11:24 ` Serge Petrenko
2020-07-03 21:29 ` Vladislav Shpilevoy
2020-07-04 17:25 ` Serge Petrenko
2020-07-06 6:48 ` Vladislav Shpilevoy
2020-07-06 7:47 ` [Tarantool-patches] [PATCH v3 0/2] fix replication tx boundaries after local space rework Kirill Yukhin
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=cover.1593696889.git.sergepetrenko@tarantool.org \
--to=sergepetrenko@tarantool.org \
--cc=gorcunov@gmail.com \
--cc=tarantool-patches@dev.tarantool.org \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v3 0/2] fix replication tx boundaries after local space rework' \
/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