From: Konstantin Osipov <kostja.osipov@gmail.com>
To: Serge Petrenko <sergepetrenko@tarantool.org>
Cc: v.shpilevoy@tarantool.org, tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v2 0/5] replication: fix local space tracking
Date: Thu, 19 Mar 2020 11:17:27 +0300 [thread overview]
Message-ID: <20200319081727.GA5707@atlas> (raw)
In-Reply-To: <cover.1584558067.git.sergepetrenko@tarantool.org>
* Serge Petrenko <sergepetrenko@tarantool.org> [20/03/18 22:52]:
> https://github.com/tarantool/tarantool/issues/4114
> https://github.com/tarantool/tarantool/tree/sp/gh-4114-local-space-replication
>
> The patchset contains 2 of Georgy's patches perorming WAL gc rework.
> The first patch introduces a matrix clock structure, which contains the latest
> known vclocks of all the cluster members and can be used to build a vclock,
> which is less than or equal to all the member vclocks.
> Such a vclock is used then in the second patch, where gc is rewritten to stop
> tracking needed WAL files by vclock signature. Now replica vclocks are used to
> define which files are still needed.
One more follow up. While I don't like the approach with matrix
clock, I accept there may be an issue with the current way GC
subsystem tracks replicas.
Could you add issue description to the changeset comment? What's
the problem with using clock signature to keep track of relays?
And if there is an issue with gc signature, let's switch to
vclocks instead, but why build a matrix?
--
Konstantin Osipov, Moscow, Russia
prev parent reply other threads:[~2020-03-19 8:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 19:47 Serge Petrenko
2020-03-18 19:47 ` [Tarantool-patches] [PATCH v2 1/5] box: introduce matrix clock Serge Petrenko
2020-03-18 20:08 ` Konstantin Osipov
2020-03-19 8:11 ` Timur Safin
2020-03-19 8:41 ` 'Konstantin Osipov'
2020-03-19 9:17 ` Sergey Ostanevich
2020-03-19 11:28 ` Serge Petrenko
2020-03-19 11:56 ` Konstantin Osipov
2020-03-19 11:59 ` Serge Petrenko
2020-03-18 19:47 ` [Tarantool-patches] [PATCH v2 2/5] wal: track consumer vclock and collect logs in wal thread Serge Petrenko
2020-03-18 19:47 ` [Tarantool-patches] [PATCH v2 3/5] vclock: add an ability to set individual clock components Serge Petrenko
2020-03-18 20:10 ` Konstantin Osipov
2020-03-19 11:31 ` Serge Petrenko
2020-03-18 19:47 ` [Tarantool-patches] [PATCH v2 4/5] replication: hide 0-th vclock components in replication responses Serge Petrenko
2020-03-18 19:47 ` [Tarantool-patches] [PATCH v2 5/5] box: start counting local space requests separately Serge Petrenko
2020-03-18 21:12 ` [Tarantool-patches] [PATCH v2 0/5] replication: fix local space tracking Vladislav Shpilevoy
2020-03-19 8:17 ` Konstantin Osipov [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=20200319081727.GA5707@atlas \
--to=kostja.osipov@gmail.com \
--cc=sergepetrenko@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v2 0/5] 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