On Sunday 19 of July 2020 21:40:38 Mike Bird wrote:
> 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
>
Hi,
I'm afraid that will require a slightly more complex solution.
Redirector selects the mirror primarily based on GeoIP information.
Therefore, it is very likely that in the current configuration, the same
backend will be selected repeatedly in the case of MirrorService.org (in
case both urls are accessible and updated). And that would make it
impossible to use a balancer on the MirrorService.org side.
The ideal solution would probably be to add the "base URL" and "backend
URLs" option to the mirror configuration. A "base URL" would be used for
address listing and redirection. To test the usability of the mirror, all
available "backend URLs" would then be tested and the overall status of
the mirror would be determined by whether at least one "backend URL" is
accessible and at the same time whether all of the accessible "backend
URLs" are updated.
What is your opinion on this idea? This should ensure reliable operation
for use with the redirector, while allowing proper use of the balancer on
the MirrorService.org side.
Cheers
--
Sl�vek
Attachments: