Tarantool development patches archive
 help / color / mirror / Atom feed
From: Georgy Kirichenko <georgy@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Georgy Kirichenko <georgy@tarantool.org>
Subject: [tarantool-patches] [PATCH 0/2] Transaction boundaries in replication protocol
Date: Sun,  6 Jan 2019 00:26:04 +0300	[thread overview]
Message-ID: <cover.1546723156.git.georgy@tarantool.org> (raw)

This patchset introduces transactional replication and consist of two
commits:
 * the first one forms transaction boundaries in a xstream
 * the second one forms transactions in applier buffers and then applies
 * them with correct begin/commit boundaries.

Note: distributed transaction are not supported so journal forms a separate
transaction for all local triggers effects.

Georgy Kirichenko (2):
  Journal transaction boundaries
  Transaction support for applier

 src/box/applier.cc         | 202 ++++++++++++++++++++++++++-----------
 src/box/iproto_constants.h |   3 +
 src/box/wal.c              |  33 +++++-
 src/box/xrow.c             |  38 +++++++
 src/box/xrow.h             |   5 +-
 test/unit/xrow.cc          |   3 +
 test/vinyl/errinj.result   |   8 +-
 test/vinyl/info.result     |  38 +++----
 test/vinyl/layout.result   |  24 ++---
 9 files changed, 260 insertions(+), 94 deletions(-)

-- 
2.20.1

             reply	other threads:[~2019-01-05 21:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-05 21:26 Georgy Kirichenko [this message]
2019-01-05 21:26 ` [tarantool-patches] [PATCH 2/2] Transaction support for applier Georgy Kirichenko
     [not found] ` <24452370cdb749e9bd8ff745947dd903b563be5e.1546723156.git.georgy@tarantool.org>
2019-01-06 13:07   ` [tarantool-patches] Re: [PATCH 1/2] Journal transaction boundaries Georgy Kirichenko

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.1546723156.git.georgy@tarantool.org \
    --to=georgy@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='Re: [tarantool-patches] [PATCH 0/2] Transaction boundaries in replication protocol' \
    /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