From: Vladimir Davydov <vdavydov.dev@gmail.com> To: Konstantin Osipov <kostja@tarantool.org> Cc: tarantool-patches@freelists.org Subject: Re: [RFC PATCH 06/12] box: refactor hot standby recovery Date: Fri, 8 Jun 2018 09:43:02 +0300 [thread overview] Message-ID: <20180608064302.2xmkbnwwaovy5kg6@esperanza> (raw) In-Reply-To: <20180608044045.GO6866@chai> On Fri, Jun 08, 2018 at 07:40:45AM +0300, Konstantin Osipov wrote: > * Vladimir Davydov <vdavydov.dev@gmail.com> [18/06/06 20:45]: > > Currently, we start a hot standby fiber even if not in hot standby mode > > (see recovery_follow_local). And we scan the wal directory twice - first > > time in recovery_follow_local(), second time in recovery_finalize(). > > Let's factor out recover_remaining_wals() from those functions and call > > it explicitly. And let's start call follow_local() and stop_local() only > > if in hot standby mode. > > In hot standby mode, we need to make sure we scan all the WALs at > least once after we acquired a path lock. > > As far as I understand this patch, it removes this property. No, it doesn't. See, even though it removes recover_remaining_wals() from recovery_finalize(), it makes hot_standby_f() call it before returning, so that we will rescan the xlog dir just before leaving hot standby mode: > @@ -490,6 +486,7 @@ hot_standby_f(va_list ap) > > subscription.events = 0; > } > + recover_remaining_wals(r, stream, NULL, true); > return 0; > }
next prev parent reply other threads:[~2018-06-08 6:43 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-06-06 17:45 [RFC PATCH 00/12] Replica rejoin Vladimir Davydov 2018-06-06 17:45 ` [RFC PATCH 01/12] recovery: drop unused recovery_exit Vladimir Davydov 2018-06-08 4:13 ` Konstantin Osipov 2018-06-06 17:45 ` [RFC PATCH 02/12] recovery: constify vclock argument Vladimir Davydov 2018-06-08 4:14 ` Konstantin Osipov 2018-06-06 17:45 ` [RFC PATCH 03/12] applier: remove extra new line in log message printed on connect Vladimir Davydov 2018-06-08 4:15 ` Konstantin Osipov 2018-06-06 17:45 ` [RFC PATCH 04/12] xrow: add helper function for encoding vclock Vladimir Davydov 2018-06-08 4:16 ` Konstantin Osipov 2018-06-06 17:45 ` [RFC PATCH 05/12] box: retrieve instance uuid before starting local recovery Vladimir Davydov 2018-06-08 4:22 ` Konstantin Osipov 2018-06-06 17:45 ` [RFC PATCH 06/12] box: refactor hot standby recovery Vladimir Davydov 2018-06-08 4:40 ` Konstantin Osipov 2018-06-08 6:43 ` Vladimir Davydov [this message] 2018-06-08 13:15 ` Konstantin Osipov 2018-06-08 13:30 ` Vladimir Davydov 2018-06-06 17:45 ` [RFC PATCH 07/12] box: retrieve end vclock before starting local recovery Vladimir Davydov 2018-06-06 17:45 ` [RFC PATCH 08/12] box: open the port " Vladimir Davydov 2018-06-06 17:45 ` [RFC PATCH 09/12] box: connect to remote peers " Vladimir Davydov 2018-06-06 17:45 ` [RFC PATCH 10/12] box: factor out local recovery function Vladimir Davydov 2018-06-06 17:45 ` [RFC PATCH 11/12] applier: inquire oldest vclock on connect Vladimir Davydov 2018-06-06 17:45 ` [RFC PATCH 12/12] replication: rebootstrap instance on startup if it fell behind Vladimir Davydov
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=20180608064302.2xmkbnwwaovy5kg6@esperanza \ --to=vdavydov.dev@gmail.com \ --cc=kostja@tarantool.org \ --cc=tarantool-patches@freelists.org \ --subject='Re: [RFC PATCH 06/12] box: refactor hot standby recovery' \ /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