From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 50040@debbugs.gnu.org
Subject: [bug#50040] [PATCH 0/2] publish: Always render nar/narinfo during backing.
Date: Tue, 31 Aug 2021 00:33:21 +0200 [thread overview]
Message-ID: <87r1eaa7gu.fsf_-_@gnu.org> (raw)
In-Reply-To: <87sfz2j5ls.fsf@gnu.org> (Mathieu Othacehe's message of "Sun, 22 Aug 2021 09:33:51 +0200")
Hi!
Mathieu Othacehe <othacehe@gnu.org> skribis:
> I think this is caused by the following lines in the Berlin Nginx
> configuration:
>
> ;; Do not tolerate slowness of hydra.gnu.org when fetching
> ;; narinfos: better return 504 quickly than wait forever.
> "proxy_connect_timeout 2s;"
> "proxy_read_timeout 2s;"
> "proxy_send_timeout 2s;"
>
> The narinfos that are not in cache yet are computed in the main thread,
> slowing down the publish process. Under pressure, computing those
> narinfo can exceed the 2s timeout resulting in the failures above.
>
> Our best course of action here could be to merge the proposed patches,
> extend the Nginx timeout to 10s and see if all the requests can be
> handled quickly enough.
Yeah, increasing these timeouts a little bit (to 5–7s? making it too
long could lead to annoyances) sounds reasonable.
Ludo’.
next prev parent reply other threads:[~2021-08-30 22:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 10:28 [bug#50040] [PATCH 0/2] publish: Always render nar/narinfo during backing Mathieu Othacehe
2021-08-13 10:30 ` [bug#50040] [PATCH 1/2] publish: Defer narinfo string creation to the http-write Mathieu Othacehe
2021-08-13 10:30 ` [bug#50040] [PATCH 2/2] publish: Remove cache bypass support Mathieu Othacehe
2021-08-30 22:31 ` [bug#50040] [PATCH 0/2] publish: Always render nar/narinfo during backing Ludovic Courtès
2021-08-31 9:08 ` Mathieu Othacehe
2021-09-01 20:48 ` Ludovic Courtès
2021-10-06 8:58 ` Mathieu Othacehe
2021-10-08 7:04 ` Mathieu Othacehe
2021-08-22 7:33 ` Mathieu Othacehe
2021-08-30 22:33 ` Ludovic Courtès [this message]
2021-09-06 13:54 ` Ludovic Courtès
2021-09-17 15:27 ` Mathieu Othacehe
2021-10-05 10:07 ` Mathieu Othacehe
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1eaa7gu.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=50040@debbugs.gnu.org \
--cc=othacehe@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).