On Sun July 19 2020 17:12:12 Sl�vek Banko wrote:
> 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.

I would imagine that is OK as we are but a tiny portion of Tim's traffic.

The important thing is not to redirect user requests for 2,000 newish
files to a server that does not have them yet.

> 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.

Maybe some kind of "partial" status on the web page if some but not all
backends are up?

> 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.

Sounds great to me.  Let's see what Tim B thinks.

--Mike