Re: A systematic way of handling Xapian lock errors?

diff --git a/91/fb972e185f83deb3d4147955a9a55efb85482c b/91/fb972e185f83deb3d4147955a9a55efb85482c
new file mode 100644 (file)
index 0000000..ded9e19
--- /dev/null
+++ b/91/fb972e185f83deb3d4147955a9a55efb85482c
@@ -0,0 +1,66 @@
+Return-Path: <david@tethera.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by arlo.cworth.org (Postfix) with ESMTP id 2E44E6DE00BD\r
+ for <notmuch@notmuchmail.org>; Tue,  2 Aug 2016 15:22:14 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.011\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[AWL=0.000,\r
+  SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id Kv3Scf1rFszg for <notmuch@notmuchmail.org>;\r
+ Tue,  2 Aug 2016 15:22:06 -0700 (PDT)\r
+Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id 2DA076DE00B8\r
+ for <notmuch@notmuchmail.org>; Tue,  2 Aug 2016 15:22:05 -0700 (PDT)\r
+Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2)\r
+ (envelope-from <david@tethera.net>)\r
+ id 1bUi4p-0004G4-VJ; Tue, 02 Aug 2016 18:22:19 -0400\r
+Received: (nullmailer pid 27041 invoked by uid 1000);\r
+ Tue, 02 Aug 2016 22:21:58 -0000\r
+From: David Bremner <david@tethera.net>\r
+To: Matt Armstrong <marmstrong@google.com>, notmuch@notmuchmail.org\r
+Subject: Re: A systematic way of handling Xapian lock errors?\r
+In-Reply-To: <qf5d1lrkx8s.fsf@marmstrong-linux.kir.corp.google.com>\r
+References: <qf5d1lrkx8s.fsf@marmstrong-linux.kir.corp.google.com>\r
+User-Agent: Notmuch/0.22.1+61~g2ce0f13 (https://notmuchmail.org) Emacs/24.5.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Wed, 03 Aug 2016 07:21:58 +0900\r
+Message-ID: <87lh0evmk9.fsf@maritornes.cs.unb.ca>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.20\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <https://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch/>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <https://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Tue, 02 Aug 2016 22:22:14 -0000\r
+\r
+Matt Armstrong <marmstrong@google.com> writes:\r
+\r
+\r
+> To address both, has something like this ever been considered:\r
+>\r
+>   notmuch --lock_timeout <seconds> COMMAND ARG...\r
+>\r
+> Then frontends like Emacs could lean on retry logic written in C.  If\r
+> this seems workable, it is something I can try implementing.\r
+\r
+notmuch in git master uses xapians lock retry if present (xapian\r
+1.3+). Currently there is no timeout, but Olly seemed receptive to the\r
+idea of adding one, so I'd suggest that's the right place to work on\r
+improving this. You may find that just having unbounded lock retries\r
+(i.e. blocking opens) is enough for your issues.\r
+\r
+d\r