From: Kirill Yukhin <kyukhin@tarantool.org>
To: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH 1/2] gc: do not abort garbage collection if failed to unlink snap file
Date: Tue, 29 Jan 2019 16:00:45 +0300 [thread overview]
Message-ID: <20190129130044.e5xgypmradidjkgc@tarantool.org> (raw)
In-Reply-To: <783662fb698347f972a57b925bf13f227b710d63.1548425270.git.vdavydov.dev@gmail.com>
Hello Vladimir,
On 25 Jan 17:34, Vladimir Davydov wrote:
> We build the checkpoint list from the list of memtx snap files. So to
> ensure that it is always possible to recover from any checkpoint present
> in box.info.gc() output, we abort garbage collection if we fail to
> unlink a snap file. This introduces extra complexity to the garbage
> collection code, which makes it difficult to make WAL file removal fully
> asynchronous.
>
> Actually, it looks like we are being way too overcautious here, because
> unlink() doesn't normally fail so an error while removing a snap file is
> highly unlikely to occur. Besides, even if it happens, it still won't be
> critical, because we never delete the last checkpoint, which is usually
> used for backups/recovery. So let's simplify the code by removing that
> check.
>
> Needed for #3938
> ---
> https://github.com/tarantool/tarantool/issues/3938
> https://github.com/tarantool/tarantool/commits/dv/gh-3938-async-wal-file-removal
I've committed the patchset into 2.1 branch.
Could you pls backport it to 1.10 as well?
--
Regards, Kirill Yukhin
next prev parent reply other threads:[~2019-01-29 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 14:34 Vladimir Davydov
2019-01-25 14:34 ` [PATCH 2/2] wal: remove old xlog files asynchronously Vladimir Davydov
2019-01-29 13:00 ` Kirill Yukhin [this message]
2019-01-29 13:57 ` [tarantool-patches] Re: [PATCH 1/2] gc: do not abort garbage collection if failed to unlink snap file 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=20190129130044.e5xgypmradidjkgc@tarantool.org \
--to=kyukhin@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH 1/2] gc: do not abort garbage collection if failed to unlink snap file' \
/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