From: Georgy Kirichenko <georgy@tarantool.org>
To: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH 0/5] Strong sequentially LSN in journal
Date: Fri, 11 Jan 2019 16:31:45 +0300 [thread overview]
Message-ID: <7270106.Yd7cKyjVDs@localhost> (raw)
In-Reply-To: <cover.1546593619.git.georgy@tarantool.org>
[-- Attachment #1: Type: text/plain, Size: 1604 bytes --]
Branch: https://github.com/tarantool/tarantool/tree/g.kirichenko/gh-980-disable-lsn-gaps
Issue: https://github.com/tarantool/tarantool/issues/980
On Friday, January 4, 2019 1:34:10 PM MSK you wrote:
> The patchset eliminates LSN gaps from journal what is needed for
> synchronous replication to enforce data stream consistency.
> Replicaset vclock is promoted only after write, replication row applying
> is allowed only if previous row was processed. All conflicting rows to skip
> are replacing with NOPs to fill gaps. After all vclock following
> protected with assert to ensure that this is strict one step increase.
>
> Needed for: #980
>
> Georgy Kirichenko (5):
> Do not promote wal vclock for failed writes
> Update replicaset vclock from wal
> Enforce applier out of order protection
> Emit NOP if an applier skips row
> Disallow lsn gaps while vclock following
>
> src/box/applier.cc | 113 ++++++++++++++++--------------
> src/box/box.cc | 3 +-
> src/box/replication.cc | 2 +
> src/box/replication.h | 3 +
> src/box/vclock.c | 16 ++++-
> src/box/vclock.h | 3 +
> src/box/wal.c | 57 ++++++---------
> src/box/xrow.c | 2 +-
> test/unit/vclock.cc | 10 +--
> test/xlog-py/dup_key.result | 12 +++-
> test/xlog-py/dup_key.test.py | 18 +++--
> test/xlog/errinj.result | 1 -
> test/xlog/panic_on_lsn_gap.result | 65 +++++++++--------
> 13 files changed, 167 insertions(+), 138 deletions(-)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-01-11 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 10:34 [tarantool-patches] " Georgy Kirichenko
2019-01-04 10:34 ` [tarantool-patches] [PATCH 1/5] Do not promote wal vclock for failed writes Georgy Kirichenko
2019-01-04 10:34 ` [tarantool-patches] [PATCH 2/5] Update replicaset vclock from wal Georgy Kirichenko
2019-01-04 10:34 ` [tarantool-patches] [PATCH 3/5] Enforce applier out of order protection Georgy Kirichenko
2019-01-04 10:34 ` [tarantool-patches] [PATCH 4/5] Emit NOP if an applier skips row Georgy Kirichenko
2019-01-04 10:34 ` [tarantool-patches] [PATCH 5/5] Disallow lsn gaps while vclock following Georgy Kirichenko
2019-01-11 13:31 ` Georgy Kirichenko [this message]
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=7270106.Yd7cKyjVDs@localhost \
--to=georgy@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH 0/5] Strong sequentially LSN in journal' \
/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