From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/27859] New: reused debuginfod_client objects don't clean out curl handles enough
Date: Thu, 13 May 2021 01:26:42 +0000 [thread overview]
Message-ID: <bug-27859-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27859
Bug ID: 27859
Summary: reused debuginfod_client objects don't clean out curl
handles enough
Product: elfutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: debuginfod
Assignee: fche at redhat dot com
Reporter: fche at redhat dot com
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
Not long after deploying the new 0.184 release in anger, amerey noticed that it
was possible for a federating debuginfod to report 404's on queries that its
upstream can readily satisfy. Further digging and testing indicates that this
is not related to the 000 negative caching, but rather some sort of
error-latching effect with the curl handles.
In a sequence of queries on the same debuginfod_client, as long as they are all
successful, things are fine. Once there is a 404 error however, this appears
to latch, and subsequent requests give 404 whether or not they were resolvable
by upstream.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-05-13 1:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 1:26 fche at redhat dot com [this message]
2021-05-13 1:27 ` [Bug debuginfod/27859] " fche at redhat dot com
2021-05-14 13:15 ` [Bug debuginfod/27859] New: " Mark Wielaard
2021-05-14 13:16 ` [Bug debuginfod/27859] " mark at klomp dot org
2021-05-16 21:51 ` fche at redhat 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-27859-10460@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).