From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/29982] sqlite errors when searching
Date: Tue, 10 Jan 2023 14:35:34 +0000 [thread overview]
Message-ID: <bug-29982-10460-Kl9eTiksmH@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29982-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29982
--- Comment #9 from Frank Ch. Eigler <fche at redhat dot com> ---
Perhaps a complete highly verbose trace (-vvv) would help identify the cause.
Scanning threads should not be able to lock each other out for O(1sec) from
sqlite operations in normal circumstances. OTOH, one can rest assured that in
case of such sqlite problems, debuginfod just treats them as transient and
retries the related scan operation later. Webapi service threads do not
contend with the others at all, so clients don't see these transient errors.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-10 14:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 10:54 [Bug debuginfod/29982] New: " ross at burtonini dot com
2023-01-10 11:27 ` [Bug debuginfod/29982] " ross at burtonini dot com
2023-01-10 11:28 ` fche at redhat dot com
2023-01-10 11:33 ` ross at burtonini dot com
2023-01-10 11:35 ` ross at burtonini dot com
2023-01-10 11:38 ` ross at burtonini dot com
2023-01-10 11:45 ` fche at redhat dot com
2023-01-10 11:47 ` ross at burtonini dot com
2023-01-10 11:50 ` ross at burtonini dot com
2023-01-10 14:35 ` fche at redhat dot com [this message]
2023-01-10 16:50 ` ross at burtonini dot com
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=bug-29982-10460-Kl9eTiksmH@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).