From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 0/4] extindex: checkpoints, graceful shutdown, cleanups
Date: Fri, 13 Nov 2020 11:11:40 +0000 [thread overview]
Message-ID: <20201113111144.23038-1-e@80x24.org> (raw)
Patches 1 and 4 should make long indexing runs more
user-friendly by being interrupt-friendly (via SIGINT, SIGQUIT,
or SIGTERM, just like read-only daemons).
I would've found this feature useful when dealing with unplanned
emergency shutdowns due to power outages. I may continue to
find it useful in the future since the power grid falling to
pieces and see more power outages.
Stealing UI ideas from git, SIGUSR1 also triggers a checkpoint
during indexing.
2 and 3 are just cleanups I've noticed along the way.
Eric Wong (4):
*index: checkpoints write last_commit metadata
*index: avoid per-epoch --batch-check processes
*index: discard sync->{todo} on iteration
extindex: support graceful shutdown via QUIT/INT/TERM
lib/PublicInbox/ExtSearchIdx.pm | 23 +++++++++----
lib/PublicInbox/IdxStack.pm | 18 +++++++---
lib/PublicInbox/SearchIdx.pm | 56 +++++++++++++++++--------------
lib/PublicInbox/SearchIdxShard.pm | 6 ++++
lib/PublicInbox/V2Writable.pm | 49 +++++++++++++++++++++------
t/idx_stack.t | 20 ++++++-----
6 files changed, 115 insertions(+), 57 deletions(-)
next reply other threads:[~2020-11-13 11:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 11:11 Eric Wong [this message]
2020-11-13 11:11 ` [PATCH 1/4] *index: checkpoints write last_commit metadata Eric Wong
2020-11-13 11:11 ` [PATCH 2/4] *index: avoid per-epoch --batch-check processes Eric Wong
2020-11-13 12:38 ` Kyle Meyer
2020-11-15 3:03 ` Eric Wong
2020-11-13 11:11 ` [PATCH 3/4] *index: discard sync->{todo} on iteration Eric Wong
2020-11-13 11:11 ` [PATCH 4/4] extindex: support graceful shutdown via QUIT/INT/TERM Eric Wong
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201113111144.23038-1-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).