https://bugzilla.novell.com/show_bug.cgi?id=411409
User abittner@stud.fh-heilbronn.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=411409#c2
--- Comment #2 from andreas bittner 2008-07-25 09:36:00 MDT ---
im not an http expert, but wasnt there an http replycode that said something
like server busy for now, or please revisit at a later time again. meaning to
delay the http fetching of the metadata file.
if i understand the whole mirror concept properly, this metadata comes from
only one source: your opensuse download server. everbody gets their metadata
from there and only gets redirected (if applicable) filewise to mirrors and
such.
so during the time period of updating the metadata file on this one
masterserver, the httpd itself could actually block the delivering of the
currently being updated metadta file with a http-reply that the visting client
(yast, zypper, whatever) should revisit in like 10seconds or half a minute or
whatever the intervals would fit.
something like that? maybe that would be the safest way to handle the
metadataupdates.
503 service unavailable? and maybe implement some delay to re-try/re-fetch the
metadata again when 503 is being given.
cheers.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.