2b59640f18
Firstly, this changes the repair functionality to return Canceled errors when a repair is canceled during the Get phase. Previously, because we do not track individual errors per piece, this would just show up as a failure to download enough pieces to repair the segment, which would cause the segment to be added to the IrreparableDB, which is entirely unhelpful. Then, ignore Canceled errors in the return value of the repair worker. Apparently, when the worker returns an error, that makes Cobra exit the program with a nonzero exit code, which causes some piece of our deployment automation to freak out and page people. And when we ask the repair worker to shut down, "canceled" errors are what we _expect_, not an error case. Change-Id: Ia3eb1c60a8d6ec5d09e7cef55dea523be28e8435 |
||
|---|---|---|
| .. | ||
| reports | ||
| admin.go | ||
| api.go | ||
| billing.go | ||
| compensation.go | ||
| Dockerfile | ||
| entrypoint | ||
| gc.go | ||
| gracefulexit.go | ||
| main.go | ||
| output.go | ||
| README.md | ||
| repairer.go | ||
| satellite.yaml | ||
| 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