From: Vladimir Davydov <vdavydov.dev@gmail.com>
To: kostja@tarantool.org
Cc: tarantool-patches@freelists.org
Subject: [PATCH 0/3] Speed up recovery in case rebootstrap is not needed
Date: Fri, 15 Jun 2018 18:48:19 +0300 [thread overview]
Message-ID: <cover.1529075903.git.vdavydov.dev@gmail.com> (raw)
In-Reply-To: <20180614125920.GD959@chai>
The following patches address the comment by @kostja to the commit that
added extra scan of the last WAL file in order to find instance vclock
before proceeding to local recovery, which is needed to determine if the
instance fell too much behind its peers in the cluster and so should be
rebootstrapped:
On Thu, Jun 14, 2018 at 03:59:20PM +0300, Konstantin Osipov wrote:
> Patch #3 is OK to push, but it needs an immediate follow-up patch
> which speeds recovery up for most cases.
To speed up recovery, this patch set makes tarantool create a new empty
xlog file on shutdown and reopen it on restart.
https://github.com/tarantool/tarantool/commits/gh-461-replica-rejoin
Vladimir Davydov (3):
xlog: erase eof marker when reopening existing file for writing
wal: rollback vclock on write failure
wal: create empty xlog on shutdown
src/box/recovery.cc | 23 --------------
src/box/wal.c | 58 +++++++++++++++++++++++++++++++++--
src/box/xlog.c | 12 +++++---
test/replication/hot_standby.result | 12 ++++----
test/replication/hot_standby.test.lua | 4 +--
test/xlog-py/dup_key.result | 20 +++---------
test/xlog-py/dup_key.test.py | 29 ++++++------------
test/xlog/panic_on_lsn_gap.result | 34 +++++++++-----------
test/xlog/panic_on_lsn_gap.test.lua | 15 +++------
test/xlog/panic_on_wal_error.result | 23 +-------------
test/xlog/panic_on_wal_error.test.lua | 9 +-----
11 files changed, 106 insertions(+), 133 deletions(-)
--
2.11.0
next prev parent reply other threads:[~2018-06-15 15:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 17:34 [PATCH v2 00/11] Replica rejoin Vladimir Davydov
2018-06-08 17:34 ` [PATCH v2 01/11] box: retrieve instance uuid before starting local recovery Vladimir Davydov
2018-06-08 17:51 ` Konstantin Osipov
2018-06-08 17:34 ` [PATCH v2 02/11] box: refactor hot standby recovery Vladimir Davydov
2018-06-08 17:34 ` [PATCH v2 03/11] box: retrieve end vclock before starting local recovery Vladimir Davydov
2018-06-14 12:58 ` Konstantin Osipov
2018-06-08 17:34 ` [PATCH v2 04/11] box: open the port " Vladimir Davydov
2018-06-13 20:43 ` Konstantin Osipov
2018-06-14 8:31 ` Vladimir Davydov
2018-06-14 12:59 ` Konstantin Osipov
2018-06-15 15:48 ` Vladimir Davydov [this message]
2018-06-15 15:48 ` [PATCH 1/3] xlog: erase eof marker when reopening existing file for writing Vladimir Davydov
2018-06-27 17:09 ` Konstantin Osipov
2018-06-15 15:48 ` [PATCH 2/3] wal: rollback vclock on write failure Vladimir Davydov
2018-06-27 17:22 ` Konstantin Osipov
2018-06-15 15:48 ` [PATCH 3/3] wal: create empty xlog on shutdown Vladimir Davydov
2018-06-27 17:29 ` Konstantin Osipov
2018-06-08 17:34 ` [PATCH v2 05/11] box: connect to remote peers before starting local recovery Vladimir Davydov
2018-06-13 20:45 ` Konstantin Osipov
2018-06-14 8:34 ` Vladimir Davydov
2018-06-14 12:59 ` Konstantin Osipov
2018-06-08 17:34 ` [PATCH v2 06/11] box: factor out local recovery function Vladimir Davydov
2018-06-13 20:50 ` Konstantin Osipov
2018-06-08 17:34 ` [PATCH v2 07/11] applier: inquire oldest vclock on connect Vladimir Davydov
2018-06-13 20:51 ` Konstantin Osipov
2018-06-14 8:40 ` Vladimir Davydov
2018-06-08 17:34 ` [PATCH v2 08/11] replication: rebootstrap instance on startup if it fell behind Vladimir Davydov
2018-06-13 20:55 ` Konstantin Osipov
2018-06-14 8:58 ` Vladimir Davydov
2018-06-08 17:34 ` [PATCH v2 09/11] vinyl: simplify vylog recovery from backup Vladimir Davydov
2018-06-08 17:34 ` [PATCH v2 10/11] vinyl: pass flags to vy_recovery_new Vladimir Davydov
2018-06-13 20:56 ` Konstantin Osipov
2018-06-08 17:34 ` [PATCH v2 11/11] vinyl: implement rebootstrap support Vladimir Davydov
2018-06-10 12:02 ` 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.1529075903.git.vdavydov.dev@gmail.com \
--to=vdavydov.dev@gmail.com \
--cc=kostja@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='Re: [PATCH 0/3] Speed up recovery in case rebootstrap is not needed' \
/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