Mirrors with weight = 0 are not disabled in Mirrorbits
The story goes like this:
- Mirrors are published in
mirrors.json
and have a weight associated with them. - Previously, mirrors with weight = 0 were disabled, as the JS dispatcher did not redirect to them.
- The JS dispatcher is gone since some time, in favor of Mirrorbits, a server-side redirector.
- We have glue code that imports
mirrors.json
into Mirrorbits. - Mirrorbits does not disable mirrors with "score" (in Mirrorbits lingo) = 0. Rather, it serves them anyway with a lower priority and will disable them automatically when/if it (automatically) detects something is wrong.
- Currently, many mirrors with weight = 0 in
mirrors.json
are being used to serve files by Mirrorbits. Only 1 out of 6 was disabled due to being slow, all the others were deemed inaccessible.
We need to, at least:
-
Fix (increase) the weights of mirrors that are now accessible once again and are fast enough. -
Adapt our glue code to exclude mirrors with weight = 0 from the list of mirrors added to Mirrorbits.
Ref: #16930 (closed)
Edited by Zen Fu