public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "vi at endrift dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/30221] New: Negative cache should differentiate failure types
Date: Sat, 11 Mar 2023 01:32:33 +0000	[thread overview]
Message-ID: <bug-30221-10460@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=30221

            Bug ID: 30221
           Summary: Negative cache should differentiate failure types
           Product: elfutils
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: debuginfod
          Assignee: unassigned at sourceware dot org
          Reporter: vi at endrift dot com
                CC: elfutils-devel at sourceware dot org
  Target Milestone: ---

Having a negative cache is essential for performant lookups with debuginfod,
but it doesn't differentiate between different types of failure, e.g. transient
(timeout, interrupted, etc) and non-transient (server responded 404 or 410). A
404 error is unlikely to be resolved in as short a timespan as a transient
error, and some servers don't have great debug info coverage, not to mention
local builds. It's very annoying to have to hit tons of builds only to get a
404 so frequently, so it'd be a good idea to have different cache timeouts for
different failure types.

I looked into how the negative cache works, and it looks like it's just the
presence of a 0 byte file. Unfortunately, this means there's no metadata
associated at all, and I'm not sure how tacking on metadata should work in the
first place. xattrs perhaps?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2023-03-11  1:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11  1:32 vi at endrift dot com [this message]
2023-03-13 16:40 ` [Bug debuginfod/30221] " fche at redhat dot com
2023-03-14  1:47 ` vi at endrift dot com
2023-03-17  1:00 ` vi at endrift dot com
2023-03-17  1:08 ` fche at redhat dot com
2023-03-17  1:16 ` vi at endrift dot com
2023-03-17  1:20 ` fche at redhat dot com
2023-03-17  1:28 ` vi at endrift dot com
2023-03-17  1:30 ` vi at endrift dot com
2023-03-17 16:16 ` amerey at redhat dot com
2023-03-17 16:53 ` amerey at redhat dot com
2023-03-17 23:39 ` vi at endrift dot com
2023-03-24 11:22 ` fche at redhat dot com
2023-04-08 13:29 ` mark at klomp dot org
2023-04-21  2:04 ` 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-30221-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).