From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>
Subject: [OSSTEST PATCH 2/4] Database locking: Perl: Increase retry count
Date: Tue, 15 Dec 2015 16:26:24 +0000 [thread overview]
Message-ID: <1450196786-27361-2-git-send-email-ian.jackson@eu.citrix.com> (raw)
In-Reply-To: <1450196786-27361-1-git-send-email-ian.jackson@eu.citrix.com>
It seems to me that this deadlock might actually become fairly common
in some setups. There is little harm in trying it for 100s rather
than 20s, and there maybe some benefit.
Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
---
Osstest.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Osstest.pm b/Osstest.pm
index a39ae42..c77d960 100644
--- a/Osstest.pm
+++ b/Osstest.pm
@@ -282,7 +282,7 @@ sub db_retry ($$$;$$) {
my ($pre,$body) =
(ref $code eq 'ARRAY') ? @$code : (sub { }, $code);
- my $retries= 20;
+ my $retries= 100;
my $r;
local $db_retry_stop;
for (;;) {
--
1.7.10.4
next prev parent reply other threads:[~2015-12-15 16:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 16:26 [OSSTEST PATCH 1/4] Database locking: Perl: Retry all deadlocks in PostgreSQL Ian Jackson
2015-12-15 16:26 ` Ian Jackson [this message]
2015-12-15 16:33 ` [OSSTEST PATCH 2/4] Database locking: Perl: Increase retry count Ian Campbell
2015-12-15 16:26 ` [OSSTEST PATCH 3/4] Database locking: Tcl: Cover LOCK TABLEs with catch Ian Jackson
2015-12-15 16:34 ` Ian Campbell
2015-12-15 16:26 ` [OSSTEST PATCH 4/4] Database locking: Tcl: Limit number of retries Ian Jackson
2015-12-15 16:35 ` Ian Campbell
2015-12-15 16:33 ` [OSSTEST PATCH 1/4] Database locking: Perl: Retry all deadlocks in PostgreSQL Ian Campbell
2015-12-15 16:41 ` Ian Jackson
2015-12-15 16:47 ` Ian Campbell
2015-12-15 17:01 ` Ian Jackson
2015-12-15 17:20 ` Ian Jackson
2015-12-16 1:39 ` Robert Hu
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=1450196786-27361-2-git-send-email-ian.jackson@eu.citrix.com \
--to=ian.jackson@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=xen-devel@lists.xenproject.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.
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 NNTP newsgroup(s).