| Summary: | Mirror status may be misleading | ||
|---|---|---|---|
| Product: | Websites | Reporter: | Morgan Leijström <fri> |
| Component: | mirrors.mageia.org | Assignee: | Sysadmin Team <sysadmin-bugs> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Normal | CC: | bittwister2, filip.komar, mageia, pterjan, sysadmin-bugs |
| Version: | trunk | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://mirrors.mageia.org/status | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Morgan Leijström
2018-10-08 10:39:28 CEST
IIUC it's not how it works. There is a timestamp on mirrors: http://ftp.acc.umu.se/mirror/mageia/mageia_timestamp Although it looks as you describe I guess on big changes like distrorebuilds I guess they just choke for sometime. CC:
(none) =>
filip.komar OK... But what i saw yesterday was that the mga6 i586 and x86_64 was orange, but all other green. I would expect cauldron to lag during mass rebuild, but not the other? Yea, dont use lot of time for this quirk, if any, better focus on 17400 :) maybe the status page should compare to the generated timestamp on master. This would solve this, and is no big deal. CC:
(none) =>
mageia First step would be to explain at the top what the page shows. The main problem is that we don't have history of when the mirror changed. If the most recent update (or upload to updates_testing) was 3 days ago, the minute after the master mirror got updated, it says all mirrors are 3 days behind. The most obvious alternative, checking how old the master mirror is and if mirrors have it would have the opposite effect: It would be all green when new updates have just been pushed even if the mirror didn't sync for a year. CC:
(none) =>
pterjan (In reply to Pascal Terjan from comment #5) > First step would be to explain at the top what the page shows. +1 > The main problem is that we don't have history of when the mirror changed. That would be clear if mageia_timestamp would be refreshed every hour regardless of any other update. (In reply to Filip Komar from comment #6) > (In reply to Pascal Terjan from comment #5) > > First step would be to explain at the top what the page shows. > +1 Yep that too :) ( And maybe a link, Bug 23651 ) > > The main problem is that we don't have history of when the mirror changed. > That would be clear if mageia_timestamp would be refreshed every hour > regardless of any other update. That seems to me to be the most clean solution. (In reply to Morgan Leijström from comment #0) > Description of problem: > > When there have not been updates issued for say two days, the mirrors have > not received updates for long. > > If then some update is generated, all mirrors are listed as being more than > 2 days out of sync. > > While i understand how this happens, it do not look good. > > Could it be redesigned so it calculates the time from when the last update > was pushed? Why not an hourly timestamp in each /media/core/release/media_info/ directory. That way Official could show green and Cauldron might show up as old/stale. I say that because I thought years ago one site had some failure which had a good Official copy and a bad Cauldron copy. If nothing else just have the current stamp updated hourly. CC:
(none) =>
bittwister2 |