From: Vladislav Shpilevoy via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Serge Petrenko <sergepetrenko@tarantool.org>, gorcunov@gmail.com
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v3 06/10] raft: keep track of greatest known term and filter replication sources based on that
Date: Sat, 17 Apr 2021 00:13:03 +0200 [thread overview]
Message-ID: <c042ff41-8741-1782-8675-17828d8b39c1@tarantool.org> (raw)
In-Reply-To: <42d09549-d7f5-9a44-b1f5-b7a6defe6be5@tarantool.org>
>>> + /**
>>> + * Latest terms received with PROMOTE entries from remote instances.
>>> + * Raft uses them to determine data from which sources may be applied.
>>> + */
>>> + struct vclock term_map;
>> 7. I have a feeling it is similar to the limbo's LSN map. Like
>> they should be merged into something one. Can't formulate that
>> properly. I hope we will see it more clear when will move all that
>> to the WAL thread someday.
>
> Yes, they're quite similar.
>
> Do you mean we should create some new structure instead of using vclock for
> these entities? Like something which would incorporate remote state:
> a map of ids with their known terms and confirmed lsns?
Yes, I think we might end up with that. We already have struct replica
doing similar, but they are not in WAL thread.
next prev parent reply other threads:[~2021-04-16 22:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 14:17 [Tarantool-patches] [PATCH v3 00/10] raft: introduce manual elections and fix a bug with re-applying rolled back transactions Serge Petrenko via Tarantool-patches
2021-04-14 14:17 ` [Tarantool-patches] [PATCH v3 01/10] wal: enrich row's meta information with sync replication flags Serge Petrenko via Tarantool-patches
2021-04-15 23:18 ` Vladislav Shpilevoy via Tarantool-patches
2021-04-16 7:08 ` Serge Petrenko via Tarantool-patches
2021-04-16 7:11 ` Serge Petrenko via Tarantool-patches
2021-04-16 8:57 ` Serge Petrenko via Tarantool-patches
2021-04-14 14:17 ` [Tarantool-patches] [PATCH v3 02/10] xrow: introduce a PROMOTE entry Serge Petrenko via Tarantool-patches
2021-04-15 23:19 ` Vladislav Shpilevoy via Tarantool-patches
2021-04-16 16:18 ` Serge Petrenko via Tarantool-patches
2021-04-14 14:17 ` [Tarantool-patches] [PATCH v3 03/10] box: actualise iproto_key_type array Serge Petrenko via Tarantool-patches
2021-04-14 14:17 ` [Tarantool-patches] [PATCH v3 04/10] box: make clear_synchro_queue() write a PROMOTE entry instead of CONFIRM + ROLLBACK Serge Petrenko via Tarantool-patches
2021-04-15 23:20 ` Vladislav Shpilevoy via Tarantool-patches
2021-04-16 9:28 ` Serge Petrenko via Tarantool-patches
2021-04-16 14:03 ` Serge Petrenko via Tarantool-patches
2021-04-14 14:17 ` [Tarantool-patches] [PATCH v3 05/10] box: write PROMOTE even for empty limbo Serge Petrenko via Tarantool-patches
2021-04-15 23:21 ` Vladislav Shpilevoy via Tarantool-patches
2021-04-16 9:33 ` Serge Petrenko via Tarantool-patches
2021-04-14 14:17 ` [Tarantool-patches] [PATCH v3 06/10] raft: keep track of greatest known term and filter replication sources based on that Serge Petrenko via Tarantool-patches
2021-04-15 23:27 ` Vladislav Shpilevoy via Tarantool-patches
2021-04-16 14:16 ` Serge Petrenko via Tarantool-patches
2021-04-16 22:13 ` Vladislav Shpilevoy via Tarantool-patches [this message]
2021-04-14 14:17 ` [Tarantool-patches] [PATCH v3 07/10] replication: introduce a new election mode: "manual" Serge Petrenko via Tarantool-patches
2021-04-15 23:27 ` Vladislav Shpilevoy via Tarantool-patches
2021-04-16 14:18 ` Serge Petrenko via Tarantool-patches
2021-04-14 14:17 ` [Tarantool-patches] [PATCH v3 08/10] Support manual elections in `box.ctl.clear_synchro_queue()` Serge Petrenko via Tarantool-patches
2021-04-15 23:30 ` Vladislav Shpilevoy via Tarantool-patches
2021-04-16 15:38 ` Serge Petrenko via Tarantool-patches
2021-04-16 15:40 ` Serge Petrenko via Tarantool-patches
2021-04-16 15:50 ` Serge Petrenko via Tarantool-patches
2021-04-14 14:17 ` [Tarantool-patches] [PATCH v3 09/10] box: remove parameter from clear_synchro_queue Serge Petrenko via Tarantool-patches
2021-04-14 14:18 ` [Tarantool-patches] [PATCH v3 10/10] box.ctl: rename clear_synchro_queue to promote Serge Petrenko via Tarantool-patches
2021-04-15 23:31 ` Vladislav Shpilevoy via Tarantool-patches
2021-04-16 16:13 ` Serge Petrenko via Tarantool-patches
2021-04-14 18:21 ` [Tarantool-patches] [PATCH v3 00/10] raft: introduce manual elections and fix a bug with re-applying rolled back transactions Cyrill Gorcunov via Tarantool-patches
2021-04-15 23:16 ` Vladislav Shpilevoy via Tarantool-patches
2021-04-16 16:35 ` Serge Petrenko via Tarantool-patches
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=c042ff41-8741-1782-8675-17828d8b39c1@tarantool.org \
--to=tarantool-patches@dev.tarantool.org \
--cc=gorcunov@gmail.com \
--cc=sergepetrenko@tarantool.org \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v3 06/10] raft: keep track of greatest known term and filter replication sources based on that' \
/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