From: Serge Petrenko <sergepetrenko@tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v5 0/4] replication: fix local space tracking
Date: Tue, 31 Mar 2020 14:24:13 +0300 [thread overview]
Message-ID: <EEEE5C2A-186F-4955-8C21-05CE3A9725F2@tarantool.org> (raw)
In-Reply-To: <cover.1585565637.git.sergepetrenko@tarantool.org>
> 30 марта 2020 г., в 14:04, Serge Petrenko <sergepetrenko@tarantool.org> написал(а):
>
> https://github.com/tarantool/tarantool/issues/4114
> https://github.com/tarantool/tarantool/tree/sp/gh-4114-local-space-replication
>
> Changes in v5:
> - review fixes as per review from Kostja
>
> Changes in v4:
> - review fixes as per review from Kostja
>
> Changes in v3:
> - rewrite the patches re wal gc rework
> to avoid matrix clock.
>
> Changes in v2:
> - used Georgy's patches re introduction of
> matrix clock and wal gc rework to fix the
> problem with ordering gc consumers by
> vclock signature
>
> Serge Petrenko (4):
> vclock: add an ability to reset individual clock components
> replication: hide 0-th vclock components in replication responses
> gc: rely on minimal vclock components instead of signatures
> box: start counting local space requests separately
>
> src/box/applier.cc | 4 +-
> src/box/box.cc | 29 +++-
> src/box/gc.c | 41 +++---
> src/box/recovery.cc | 8 +-
> src/box/relay.cc | 21 +--
> src/box/vclock.c | 15 +++
> src/box/vclock.h | 102 ++++++++++++++
> src/box/wal.c | 16 ++-
> test/replication/anon.result | 5 +
> test/replication/anon.test.lua | 2 +
> test/replication/autobootstrap.result | 6 +
> test/replication/autobootstrap.test.lua | 2 +
> test/replication/before_replace.result | 8 +-
> test/replication/before_replace.test.lua | 4 +-
> .../gh-4114-local-space-replication.result | 125 ++++++++++++++++++
> .../gh-4114-local-space-replication.test.lua | 48 +++++++
> test/replication/local_spaces.result | 4 +
> test/replication/local_spaces.test.lua | 3 +
> test/replication/misc.result | 6 +
> test/replication/misc.test.lua | 2 +
> test/replication/quorum.result | 6 +
> test/replication/quorum.test.lua | 2 +
> test/replication/replica_rejoin.result | 9 ++
> test/replication/replica_rejoin.test.lua | 3 +
> test/replication/skip_conflict_row.result | 3 +
> test/replication/skip_conflict_row.test.lua | 1 +
> test/replication/suite.cfg | 1 +
> test/vinyl/errinj.result | 5 +
> test/vinyl/errinj.test.lua | 4 +
> 29 files changed, 442 insertions(+), 43 deletions(-)
> create mode 100644 test/replication/gh-4114-local-space-replication.result
> create mode 100644 test/replication/gh-4114-local-space-replication.test.lua
>
> --
> 2.21.1 (Apple Git-122.3)
>
The patchset needs a changelog entry.
Sorry for late posting, here’s one:
@ChangeLog:
- local space operations are now counted in 0th vclock
component. Every instance may have its own 0-th vclock
component not matching others’. Local space operations
are not replicated at all, even as NOPs. (gh-4114)
- gc consumers are now ordered by their vclocks and not
by vclock signatures. Only the WALS that contain no
entries needed by any of the consumers are deleted. (gh-4114)
--
Serge Petrenko
sergepetrenko@tarantool.org
next prev parent reply other threads:[~2020-03-31 11:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 11:04 Serge Petrenko
2020-03-30 11:04 ` [Tarantool-patches] [PATCH v5 1/4] vclock: add an ability to reset individual clock components Serge Petrenko
2020-03-30 12:56 ` Konstantin Osipov
2020-04-04 20:51 ` Vladislav Shpilevoy
2020-04-06 8:39 ` Konstantin Osipov
2020-04-07 11:48 ` Serge Petrenko
2020-03-30 11:04 ` [Tarantool-patches] [PATCH v5 2/4] replication: hide 0-th vclock components in replication responses Serge Petrenko
2020-03-30 12:56 ` Konstantin Osipov
2020-04-04 20:51 ` Vladislav Shpilevoy
2020-04-06 8:38 ` Konstantin Osipov
2020-04-07 12:22 ` Serge Petrenko
2020-03-30 11:04 ` [Tarantool-patches] [PATCH v5 3/4] gc: rely on minimal vclock components instead of signatures Serge Petrenko
2020-03-30 12:57 ` Konstantin Osipov
2020-04-04 20:51 ` Vladislav Shpilevoy
2020-04-07 12:40 ` Serge Petrenko
2020-03-30 11:04 ` [Tarantool-patches] [PATCH v5 4/4] box: start counting local space requests separately Serge Petrenko
2020-03-30 12:58 ` Konstantin Osipov
2020-04-04 20:51 ` Vladislav Shpilevoy
2020-04-07 15:48 ` Serge Petrenko
2020-03-31 11:24 ` Serge Petrenko [this message]
2020-04-04 20:51 ` [Tarantool-patches] [PATCH v5 0/4] replication: fix local space tracking Vladislav Shpilevoy
2020-04-07 11:15 ` Serge Petrenko
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=EEEE5C2A-186F-4955-8C21-05CE3A9725F2@tarantool.org \
--to=sergepetrenko@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v5 0/4] replication: fix local space tracking' \
/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