19 Jul
2020
19 Jul
'20
7:40 p.m.
On Sun July 19 2020 11:53:17 Slávek Banko wrote:
A small disadvantage compared to the current state
will be that when using
one record for your mirror system, the redirector may obtain inaccurate
information about the state of the mirror, because it will not be certain
which of your backends has been contacted. Specifically, the redirector
may get a different state than the real user will subsequently receive.
Hi Slávek,
I'm wondering whether we can decouple the web page status from the
redirector. We could continue to use kuiper and copernicus for the
redirector as they rsync from us independently.
However Tim would prefer that kuiper and copernicus not be publicized
and is asking that the mirror status page show their load balancer
rather than kuiper and copernicus.
Copernicus is currently rebuilding but even before that there were
often distinct differences, e.g. 2461 files difference between
kuiper and copernicus during primary mirror's daily report on June 9th:
0 files missing from
copernicus.mirrorservice.org::trinitydesktop.org/
2461 files missing from kuiper.mirrorservice.org::trinitydesktop.org/
--Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting