From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: Serge Petrenko <sergepetrenko@tarantool.org>, gorcunov@gmail.com
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v2 6/6] txn_limbo: ignore CONFIRM/ROLLBACK for a foreign master
Date: Wed, 23 Dec 2020 18:28:06 +0100 [thread overview]
Message-ID: <ff674725-b2b0-f8c3-3b1a-89e3ec827f89@tarantool.org> (raw)
In-Reply-To: <b21832c41b36f61f98a59f39a4a26abf2d449654.1608724239.git.sergepetrenko@tarantool.org>
Thanks for the patch!
On 23.12.2020 12:59, Serge Petrenko via Tarantool-patches wrote:
> We designed limbo so that it errors on receiving a CONFIRM or ROLLBACK
> for other instance's data. Actually, this error is pointless, and even
> harmful. Here's why:
>
> Imagine you have 3 instances, 1, 2 and 3.
> First 1 writes some synchronous transactions, but dies before writing CONFIRM.
>
> Now 2 has to write CONFIRM instead of 1 to take limbo ownership.
> From now on 2 is the limbo owner and in case of high enough load it constantly
> has some data in the limbo.
>
> Once 1 restarts, it first recovers its xlogs, and fills its limbo with
> its own unconfirmed transactions from the previous run. Now replication
> between 1, 2 and 3 is started and the first thing 1 sees is that 2 and 3
> ack its old transactions. So 1 writes CONFIRM for its own transactions
> even before the same CONFIRM written by 2 reaches it.
> Once the CONFIRM written by 1 is replicated to 2 and 3 they error and
> stop replication, since their limbo contains entries from 2, not from 1.
> Actually, there's no need to error, since it's just a really old CONFIRM
> which's already processed by both 2 and 3.>
> So, ignore CONFIRM/ROLLBACK when it references a wrong limbo owner.
>
> The issue was discovered with test replication/election_qsync_stress.
The comment is good.
next prev parent reply other threads:[~2020-12-23 17:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 11:59 [Tarantool-patches] [PATCH v2 0/6] make clear_synchro_queue commit everything Serge Petrenko
2020-12-23 11:59 ` [Tarantool-patches] [PATCH v2 1/6] box: add a single execution guard to clear_synchro_queue Serge Petrenko
2020-12-23 11:59 ` [Tarantool-patches] [PATCH v2 2/6] relay: introduce on_status_update trigger Serge Petrenko
2020-12-23 17:25 ` Vladislav Shpilevoy
2020-12-24 16:11 ` Serge Petrenko
2020-12-23 11:59 ` [Tarantool-patches] [PATCH v2 3/6] txn_limbo: introduce txn_limbo_last_synchro_entry method Serge Petrenko
2020-12-23 17:25 ` Vladislav Shpilevoy
2020-12-24 16:13 ` Serge Petrenko
2020-12-23 11:59 ` [Tarantool-patches] [PATCH v2 4/6] box: rework clear_synchro_queue to commit everything Serge Petrenko
2020-12-23 17:28 ` Vladislav Shpilevoy
2020-12-24 16:12 ` Serge Petrenko
2020-12-24 17:35 ` Vladislav Shpilevoy
2020-12-24 21:02 ` Serge Petrenko
2020-12-23 11:59 ` [Tarantool-patches] [PATCH v2 5/6] test: fix replication/election_qsync_stress test Serge Petrenko
2020-12-23 11:59 ` [Tarantool-patches] [PATCH v2 6/6] txn_limbo: ignore CONFIRM/ROLLBACK for a foreign master Serge Petrenko
2020-12-23 17:28 ` Vladislav Shpilevoy [this message]
2020-12-24 16:13 ` Serge Petrenko
2020-12-25 10:04 ` [Tarantool-patches] [PATCH v2 0/6] make clear_synchro_queue commit everything Kirill Yukhin
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=ff674725-b2b0-f8c3-3b1a-89e3ec827f89@tarantool.org \
--to=v.shpilevoy@tarantool.org \
--cc=gorcunov@gmail.com \
--cc=sergepetrenko@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v2 6/6] txn_limbo: ignore CONFIRM/ROLLBACK for a foreign master' \
/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