From: Vladislav Shpilevoy via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Serge Petrenko <sergepetrenko@tarantool.org>,
Cyrill Gorcunov <gorcunov@gmail.com>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH 1/1] applier: process synchro rows after WAL write
Date: Fri, 9 Apr 2021 23:32:45 +0200 [thread overview]
Message-ID: <045a7eae-595a-10c4-779e-c80272eef611@tarantool.org> (raw)
In-Reply-To: <bce9294c-36cc-daf9-2546-4d1fe2e2cdac@tarantool.org>
>> I didn't try to reproduce this craziness though. However I have an idea how
>> we could fix it "for good". Introduce a fiber read-write lock. All the
>> transactions take read-lock on the limbo. All CONFIRM/ROLLBACK/PROMOTE take
>> a write-lock on the limbo. Then all the limbo owner transitions would be
>> fixed.
>
> Sounds good. Isn't it enough to only have a write lock though?
Perhaps. I didn't give it much thought yet. Maybe after this patch is pushed,
and after you introduce PROMOTE.
next prev parent reply other threads:[~2021-04-09 21:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 22:47 Vladislav Shpilevoy via Tarantool-patches
2021-04-08 8:39 ` Serge Petrenko via Tarantool-patches
2021-04-08 10:19 ` Cyrill Gorcunov via Tarantool-patches
2021-04-08 10:32 ` Serge Petrenko via Tarantool-patches
2021-04-08 10:46 ` Cyrill Gorcunov via Tarantool-patches
2021-04-08 22:57 ` Vladislav Shpilevoy via Tarantool-patches
2021-04-09 8:25 ` Serge Petrenko via Tarantool-patches
2021-04-09 21:32 ` Vladislav Shpilevoy via Tarantool-patches [this message]
2021-04-08 22:56 ` Vladislav Shpilevoy via Tarantool-patches
2021-04-09 8:26 ` 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=045a7eae-595a-10c4-779e-c80272eef611@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 1/1] applier: process synchro rows after WAL write' \
/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