modules/varnish/files/proxy-el6.vcl | 1 + modules/varnish/files/proxy.vcl | 1 + 2 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/modules/varnish/files/proxy-el6.vcl b/modules/varnish/files/proxy-el6.vcl index 384dedf..c66ebc6 100644 --- a/modules/varnish/files/proxy-el6.vcl +++ b/modules/varnish/files/proxy-el6.vcl @@ -18,6 +18,7 @@ backend mirrorlists { backend pkgdb { .host = "localhost"; .port = "10003"; + .first_byte_timeout = 90s; }
backend fas { diff --git a/modules/varnish/files/proxy.vcl b/modules/varnish/files/proxy.vcl index a92ce55..baf02d5 100644 --- a/modules/varnish/files/proxy.vcl +++ b/modules/varnish/files/proxy.vcl @@ -18,6 +18,7 @@ backend mirrorlists { backend pkgdb { .host = "localhost"; .port = "10003"; + .first_byte_timeout = 90s; }
backend fas {
Not horribly opposed, but why?
-- Matt Domsch Technology Strategist Dell | Office of the CTO
On Mon, 7 Mar 2011 12:32:37 -0600 Matt_Domsch@Dell.com wrote:
Not horribly opposed, but why?
Sorry, cut off my explanatory text there. ;(
Basically owner-sync-pkgdb hits a pkgdb url to get vcs into to populate into koji from releng02. This cron job is hitting the default 60 second timeout sometimes and failing. Increasing the timeout to 90s should allow it to always complete.
Upsides: No cron spam emails from the failed job. New package owners don't need to wait for packages to be buildable in koji until the job finishes correctly.
Downsides: not sure if there are any off hand.
kevin
On Mon, Mar 07, 2011 at 11:45:53AM -0700, Kevin Fenzi wrote:
On Mon, 7 Mar 2011 12:32:37 -0600 Matt_Domsch@Dell.com wrote:
Not horribly opposed, but why?
Sorry, cut off my explanatory text there. ;(
Basically owner-sync-pkgdb hits a pkgdb url to get vcs into to populate into koji from releng02. This cron job is hitting the default 60 second timeout sometimes and failing. Increasing the timeout to 90s should allow it to always complete.
Upsides: No cron spam emails from the failed job. New package owners don't need to wait for packages to be buildable in koji until the job finishes correctly.
Downsides: not sure if there are any off hand.
+1 from me.
Should be easy to revert if it causes problems too.
-Toshio
+1
-- Matt Domsch Technology Strategist Dell | Office of the CTO
-----Original Message----- From: infrastructure-bounces@lists.fedoraproject.org [mailto:infrastructure-bounces@lists.fedoraproject.org] On Behalf Of Kevin Fenzi Sent: Monday, March 07, 2011 12:46 PM To: Fedora Infrastructure Subject: Re: Freeze change request: increase varnish timeout for pkgdb to 90s
On Mon, 7 Mar 2011 12:32:37 -0600 Matt_Domsch@Dell.com wrote:
Not horribly opposed, but why?
Sorry, cut off my explanatory text there. ;(
Basically owner-sync-pkgdb hits a pkgdb url to get vcs into to populate into koji from releng02. This cron job is hitting the default 60 second timeout sometimes and failing. Increasing the timeout to 90s should allow it to always complete.
Upsides: No cron spam emails from the failed job. New package owners don't need to wait for packages to be buildable in koji until the job finishes correctly.
Downsides: not sure if there are any off hand.
kevin
infrastructure@lists.fedoraproject.org