Mirrorbits is a geographical download redirector written in Go for distributing files efficiently across a set of mirrors. It offers a simple and economic way to create a Content Delivery Network layer using a pure software stack. It is primarily designed for the distribution of large-scale Open-Source projects with a lot of traffic.
- Blazing fast, can reach 8K QPS on a single laptop
- Easy to deploy and maintain, everything is packed in a single binary
- Automatic synchronization with the mirrors over rsync or FTP
- Response can be either JSON or HTTP redirect
- Support partial repositories
- Complete checksum / size control
- Realtime monitoring and reports
- Disable misbehaving mirrors without human intervention
- Realtime decision making based on location, AS number and defined rules
- Smart load-balancing over multiple mirrors in the same area to avoid hotspots
- Ability to adjust the weight of each mirror
- Limit access to a country, region or ASN for any mirror
- Clustering (multiple mirrorbits instances)
- High-availability using redis-sentinel
- Realtime statistics per file / mirror / date
- Realtime reconfiguration
- Seamless binary upgrade (aka zero downtime upgrade)
- Mirmon support
- Full IPv6 support
Is it production ready?
Yet some things might change before the 1.0 release. If you intend to deploy Mirrorbits in a production system it is advised to notify the author first so we can help you to make any transition as seamless as possible!
- Redis 2.8.12 (or later)
- a recent GeoIP version 1 database from Maxmind (see contrib/geoip/)
- redis-sentinel (for high-availability support)
You can either get a prebuilt version or choose to build it yourself.
$ go get -u github.com/etix/mirrorbits $ cd $GOPATH/src/github.com/etix/mirrorbits $ make install
The resulting executable should now be in your $GOPATH/bin directory.
If you plan to use the web UI be sure to copy the templates into your system (usually in /usr/share/mirrorbits).
A sample configuration file can be found here.
|Repository||Path to your own copy of the repository|
|Templates||Path containing the templates|
|OutputMode||auto: based on the Accept header content
redirect: do an HTTP redirect to the destination
json: return a JSON formatted document (also known as API mode)
|ListenAddress||Local address and port to bind|
|Gzip||Use gzip compression for the JSON responses|
|RedisAddress||Address and port of the Redis database|
|RedisPassword||Password to access the Redis database|
|RedisSentinelMasterName||Name of the redis-sentinel cluster|
|RedisSentinels||List of redis-sentinel hosts|
|LogDir||Path to the directory where to save log files|
|GeoipDatabasePath||Path to the geoip databases|
|ConcurrentSync||Maximum number of server sync (rsync/ftp) do to simultaneously|
|ScanInterval||Interval between rsync/ftp synchronizations (in minutes)|
|CheckInterval||Interval between mirrors health’s checks (in minutes)|
|RepositoryScanInterval||Interval between scans of the local repository (in minutes, 0 to disable)|
|Hashes||List of file hashes to computes (SHA1, SHA256, MD5)|
|DisallowRedirects||Disable any mirror trying to do an HTTP redirect|
|WeightDistributionRange||Multiplier of the distance to the first mirror to find other possible mirrors in order to distribute the load|
|DisableOnMissingFile||Disable a mirror if an advertised file on rsync/ftp appears to be missing on HTTP|
|MaxLinkHeaders||Amount of backup mirror locations returned in HTTP headers|
|Fallbacks||A list of possible mirrors to use as fallback if a request fails or if the database is unreachable. These mirrors are not tracked by mirrorbits. It is assumed they have all the files available in the local repository.|
Mirrorbits is a self-contained application and can act, at the same time, as the server and the cli.
To run the server:
Additionnal options can be found with
To run the cli:
Add a mirror:
mirrorbits add -ftp="ftp://ftp.mirrors.example/myproject/" -http="http://ftp.mirrors.example/myproject/" mirrors.example
Enable the mirror:
mirrorbits enable mirrors.example
Clustering / High availability
Note: Clustering support has been added recently and should be treated as experimental.
Multiple instances of mirrorbits can be started simultanously on different servers, discovery of other nodes should be automatic as long as all the instances are connected to the same redis server. In addition to the clustering it is advised to use redis-sentinel to monitor the database and gracefuly handle failover.
Mirrorbits has a mode called seamless binary upgrade to upgrade the server executable at runtime without service disruption. Once the binary has been replaced on the filesystem just issue the following command in the cli:
- When configured in redirect mode, Mirrorbits can easily serve client requests directly but it is usually recommended to set it behind a reverse proxy like nginx. In this case take care to pass the IP address of the client within a X-Forwarded-For header:
proxy_set_header X-Forwarded-For $remote_addr;
- It is advised to never cache requests intended for Mirrorbits since each request is supposed to be unique, caching the result might have unexpected consequences.
The best place to discuss about mirrorbits is to join the #VideoLAN IRC channel on Freenode.
For the latest news, you can follow @mirrorbits on Twitter.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.