forked from Deuxfleurs/garage
S3-compatible object store for small self-hosted geo-distributed deployments
Alex
0009fd136c
Included in this PR: - [x] Small refactor, resync code is moved to a separate `block/resync.rs` file - [x] Block resync tranquility is no longer in config file, it is set dynamically using `garage worker set resync-tranquility` (this parameter is persisted over Garage restarts) - [x] Up to 4 block resync workers can be activated to run simultaneously to speed up big resyncs, this parameter is set dynamically using `garage worker set resync-n-workers` Reviewed-on: Deuxfleurs/garage#369 |
||
---|---|---|
doc | ||
nix | ||
script | ||
src | ||
.dockerignore | ||
.drone.yml | ||
.gitattributes | ||
.gitignore | ||
Cargo.lock | ||
Cargo.nix | ||
Cargo.toml | ||
default.nix | ||
Dockerfile | ||
k2v_test.py | ||
LICENSE | ||
Makefile | ||
README.md | ||
rustfmt.toml | ||
shell.nix |
Garage
[ Website and documentation | Binary releases | Git repository | Matrix channel ]
Garage is a lightweight S3-compatible distributed object store, with the following goals:
- As self-contained as possible
- Easy to set up
- Highly resilient to network failures, network latency, disk failures, sysadmin failures
- Relatively simple
- Made for multi-datacenter deployments
Non-goals include:
- Extremely high performance
- Complete implementation of the S3 API
- Erasure coding (our replication model is simply to copy the data as is on several nodes, in different datacenters if possible)
Our main use case is to provide a distributed storage layer for small-scale self hosted services such as Deuxfleurs.