From: Georgy Kirichenko <georgy@tarantool.org> To: tarantool-patches@freelists.org Cc: Georgy Kirichenko <georgy@tarantool.org> Subject: [tarantool-patches] [PATCH v2 0/5] Strong sequentially LSN in journal Date: Tue, 22 Jan 2019 13:31:08 +0300 [thread overview] Message-ID: <cover.1548152776.git.georgy@tarantool.org> (raw) 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 Changes in v2: - Rebased against latest 2.1 - Fix handling rows which were returned back Issue: https://github.com/tarantool/tarantool/issues/980 Branch:https://github.com/tarantool/tarantool/tree/g.kirichenko/gh-980-disable-lsn-gaps 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 | 120 +++++++++++++++++------------- 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, 174 insertions(+), 138 deletions(-) -- 2.20.1
next reply other threads:[~2019-01-22 10:29 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-01-22 10:31 Georgy Kirichenko [this message] 2019-01-22 10:31 ` [tarantool-patches] [PATCH v2 1/5] Do not promote wal vclock for failed writes Georgy Kirichenko 2019-01-28 11:20 ` Vladimir Davydov 2019-01-29 10:22 ` Георгий Кириченко 2019-01-29 11:58 ` Vladimir Davydov 2019-01-22 10:31 ` [tarantool-patches] [PATCH v2 2/5] Update replicaset vclock from wal Georgy Kirichenko 2019-01-28 11:59 ` Vladimir Davydov 2019-01-29 10:33 ` [tarantool-patches] " Георгий Кириченко 2019-01-22 10:31 ` [tarantool-patches] [PATCH v2 3/5] Enforce applier out of order protection Georgy Kirichenko 2019-01-28 12:09 ` Vladimir Davydov 2019-01-29 10:30 ` [tarantool-patches] " Георгий Кириченко 2019-01-29 12:00 ` Vladimir Davydov 2019-01-22 10:31 ` [tarantool-patches] [PATCH v2 4/5] Emit NOP if an applier skips row Georgy Kirichenko 2019-01-28 12:15 ` Vladimir Davydov 2019-02-08 16:50 ` [tarantool-patches] " Konstantin Osipov 2019-01-22 10:31 ` [tarantool-patches] [PATCH v2 5/5] Disallow lsn gaps while vclock following Georgy Kirichenko 2019-01-28 12:18 ` Vladimir Davydov 2019-01-28 11:15 ` [tarantool-patches] [PATCH v2 0/5] Strong sequentially LSN in journal Vladimir Davydov
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.1548152776.git.georgy@tarantool.org \ --to=georgy@tarantool.org \ --cc=tarantool-patches@freelists.org \ --subject='Re: [tarantool-patches] [PATCH v2 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