915f3952af
We avoid putting more than one piece of a segment on the same /24 network (or /64 for ipv6). However, it is possible for multiple pieces of the same segment to move to the same network over time. Nodes can change addresses, or segments could be uploaded with dev settings, etc. We will call such pieces "clumped", as they are clumped into the same net, and are much more likely to be lost or preserved together. This change teaches the repair checker to recognize segments which have clumped pieces, and put them in the repair queue. It also teaches the repair worker to repair such segments (treating clumped pieces as "retrievable but unhealthy"; i.e., they will be replaced on new nodes if possible). Refs: https://github.com/storj/storj/issues/5391 Change-Id: Iaa9e339fee8f80f4ad39895438e9f18606338908 |
||
---|---|---|
.. | ||
reports | ||
admin.go | ||
api.go | ||
auditor.go | ||
billing_test.go | ||
billing.go | ||
compensation.go | ||
Dockerfile | ||
entrypoint | ||
fetchpieces.go | ||
gc-bf.go | ||
gc.go | ||
gracefulexit.go | ||
main.go | ||
output.go | ||
rangedloop.go | ||
README.md | ||
repair_segment_test.go | ||
repair_segment.go | ||
repairer.go | ||
testdata_test.go | ||
testdata.go | ||
usage.go |
Satellite
Documentation for developing and building the satellite service
Usage:
First make an identity:
go install storj.io/storj/cmd/satellite
satellite setup
You can edit ~/.storj/satellite/config.yaml
to your liking. Then run it!
satellite run