From: David Bremner <david@tethera.net>
To: Matt Armstrong <marmstrong@google.com>, notmuch@notmuchmail.org
Subject: Re: A systematic way of handling Xapian lock errors?
Date: Wed, 03 Aug 2016 07:21:58 +0900 [thread overview]
Message-ID: <87lh0evmk9.fsf@maritornes.cs.unb.ca> (raw)
In-Reply-To: <qf5d1lrkx8s.fsf@marmstrong-linux.kir.corp.google.com>
Matt Armstrong <marmstrong@google.com> writes:
> To address both, has something like this ever been considered:
>
> notmuch --lock_timeout <seconds> COMMAND ARG...
>
> Then frontends like Emacs could lean on retry logic written in C. If
> this seems workable, it is something I can try implementing.
notmuch in git master uses xapians lock retry if present (xapian
1.3+). Currently there is no timeout, but Olly seemed receptive to the
idea of adding one, so I'd suggest that's the right place to work on
improving this. You may find that just having unbounded lock retries
(i.e. blocking opens) is enough for your issues.
d
next prev parent reply other threads:[~2016-08-02 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 15:26 A systematic way of handling Xapian lock errors? Matt Armstrong
2016-08-02 22:21 ` David Bremner [this message]
2016-08-02 22:46 ` Matt Armstrong
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lh0evmk9.fsf@maritornes.cs.unb.ca \
--to=david@tethera.net \
--cc=marmstrong@google.com \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).