S3-compatible object store for small self-hosted geo-distributed deployments
https://garagehq.deuxfleurs.fr/
Alex Auvolat
16fbb32fd3
droping the slot later (after reading the request response) means that we aren't freeing our quota slot, so the maximum number of simultaneous requests now also counts the response reading phase TODO next: quotas per rpc destination node, or maybe per datacenter (?) |
||
---|---|---|
src | ||
.gitignore | ||
Cargo.lock | ||
Cargo.toml | ||
genkeys.sh | ||
LICENSE | ||
Makefile | ||
README.md | ||
rustfmt.toml | ||
test_delete.sh | ||
test_read.sh | ||
test_write.sh | ||
TODO |
Garage
THIS IS ALL WORK IN PROGRESS. NOTHING TO SEE YET BUT THANKS FOR YOUR INTEREST.
Garage implements an S3-compatible object store with high resiliency to network failures, machine failure, and sysadmin failure.
To log:
RUST_LOG=garage=debug cargo run --release -- server -c config_file.toml
What to repair
tables
: to do a full sync of metadata, should not be necessary because it is done every hour by the systemversions
andblock_refs
: very time consuming, usefull if deletions have not been propagated, improves garbage collectionblocks
: very usefull to resync/rebalance blocks betweeen nodes