Tarantool development patches archive
 help / color / mirror / Atom feed
From: Vladimir Davydov <vdavydov.dev@gmail.com>
To: Georgy Kirichenko <georgy@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: Re: [tarantool-patches] [PATCH 0/3] Promote vclock only for successful writes
Date: Wed, 6 Feb 2019 16:50:32 +0300	[thread overview]
Message-ID: <20190206135032.q2vg54o7hj56kpgo@esperanza> (raw)
In-Reply-To: <cover.1549441084.git.georgy@tarantool.org>

This is v2 so you should've added v2 to the subject and a brief change
log to the body.

On Wed, Feb 06, 2019 at 11:29:56AM +0300, Georgy Kirichenko wrote:
> Promote tx and wal vclock only if corresponding row was successfully
> written to wal. This prevents tarantool from lsn gaps in case of an wal
> error as well as from skipped rows in case of replication errors.
> 
> Branch: https://github.com/tarantool/tarantool/tree/g.kirichenko/gh-2283-dont-skip-rows-after-errors
> Issue: https://github.com/tarantool/tarantool/issues/2283
> 
> Georgy Kirichenko (3):
>   Do not promote wal vclock for failed writes
>   Enforce applier out of order protection
>   Promote replicaset.vclock only after wal
> 
>  src/box/applier.cc                          |  46 +--
>  src/box/wal.c                               |  57 ++-
>  test/box/errinj.result                      |  23 ++
>  test/box/errinj.test.lua                    |   8 +
>  test/replication/skip_conflict_row.test.lua |  19 +
>  test/xlog-py/dup_key.result                 |  12 +-
>  test/xlog-py/dup_key.test.py                |  23 +-
>  test/xlog/errinj.result                     |   1 -
>  test/xlog/panic_on_lsn_gap.result           | 377 --------------------
>  test/xlog/panic_on_lsn_gap.test.lua         | 136 -------
>  10 files changed, 116 insertions(+), 586 deletions(-)
>  delete mode 100644 test/xlog/panic_on_lsn_gap.result
>  delete mode 100644 test/xlog/panic_on_lsn_gap.test.lua

      parent reply	other threads:[~2019-02-06 13:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06  8:29 Georgy Kirichenko
2019-02-06  8:29 ` [tarantool-patches] [PATCH 1/3] Do not promote wal vclock for failed writes Georgy Kirichenko
2019-02-06 13:56   ` Vladimir Davydov
2019-02-06  8:29 ` [tarantool-patches] [PATCH 2/3] Enforce applier out of order protection Georgy Kirichenko
2019-02-06 14:13   ` Vladimir Davydov
2019-02-06  8:29 ` [tarantool-patches] [PATCH 3/3] Promote replicaset.vclock only after wal Georgy Kirichenko
2019-02-06 14:45   ` Vladimir Davydov
2019-02-06 13:50 ` Vladimir Davydov [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=20190206135032.q2vg54o7hj56kpgo@esperanza \
    --to=vdavydov.dev@gmail.com \
    --cc=georgy@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='Re: [tarantool-patches] [PATCH 0/3] Promote vclock only for successful writes' \
    /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