From: Serge Petrenko <sergepetrenko@tarantool.org> To: Konstantin Osipov <kostja@tarantool.org> Cc: tarantool-patches@freelists.org, Vladimir Davydov <vdavydov.dev@gmail.com> Subject: Re: [tarantool-patches] [PATCH v2] memtx: add yields during index build Date: Tue, 28 May 2019 18:36:09 +0300 [thread overview] Message-ID: <AA74A9A1-7249-4146-AD83-12B9CD7B58F6@tarantool.org> (raw) In-Reply-To: <20190523152544.GA17820@atlas> > 23 мая 2019 г., в 18:25, Konstantin Osipov <kostja@tarantool.org> написал(а): > > * Serge Petrenko <sergepetrenko@tarantool.org> [19/05/23 17:58]: >> Memtx index build used to stall event loop for all the build period. >> Add occasional yields so that the loop is not blocked for too long. >> Also make index build set on_replace triggers so that concurrent >> replaces are also correctly handled during the build. >> >> Closes #3976 > > The next piece of the puzzle is we need to understand how this > replicates. > > What would be the order of such a concurrent execution on replica? > > I'd assume it would stop the applier until the build is finished, > is this right, Georgy? Georgy says that’s right, applier holds the latch until wal write happens, i.e. during the whole index build process > > I think this is the only reasonable and safe thing to do, do you > have other opinions? > > If no, we just need to test it with some timeout injections on > replica, in particular add a test which breaks replication by > inserting a conflicting row while the index is being built. > This test would be useful for both engines, I guess. > > -- > Konstantin Osipov, Moscow, Russia
next prev parent reply other threads:[~2019-05-28 15:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-23 14:11 Serge Petrenko 2019-05-23 15:25 ` [tarantool-patches] " Konstantin Osipov 2019-05-28 15:36 ` Serge Petrenko [this message] 2019-05-27 16:45 ` Vladimir Davydov 2019-05-28 15:34 ` 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=AA74A9A1-7249-4146-AD83-12B9CD7B58F6@tarantool.org \ --to=sergepetrenko@tarantool.org \ --cc=kostja@tarantool.org \ --cc=tarantool-patches@freelists.org \ --cc=vdavydov.dev@gmail.com \ --subject='Re: [tarantool-patches] [PATCH v2] memtx: add yields during index build' \ /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