3501656e98
Reputation updates during repair currently consumes a lot of database resources. Sometimes increasing the rate of repair is more important than auditing a node based on whether they have or don't have the correct piece during repair. This is the job of the audit service. This commit is to implement an intermediate solution from this issue: https://github.com/storj/storj/issues/5089 This commit does not address the more in-depth fix discussed here: https://github.com/storj/storj/issues/4939 Change-Id: I4163b18d78a96fadf5265789fd73c8aa8def0e9f |
||
|---|---|---|
| .. | ||
| reports | ||
| admin.go | ||
| api.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 | ||
| satellite.yaml | ||
| 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