78c6d5bb32
this commit introduces the reported_serials table. its purpose is to allow for blind writes into it as nodes report in so that we have minimal contention. in order to continue to accurately account for used bandwidth, though, we cannot immediately add the settled amount. if we did, we would have to give up on blind writes. the table's primary key is structured precisely so that we can quickly find expired orders and so that we maximally benefit from rocksdb path prefix compression. we do this by rounding the expires at time forward to the next day, effectively giving us storagenode petnames for free. and since there's no secondary index or foreign key constraints, this design should use significantly less space than the current used_serials table while also reducing contention. after inserting the orders into the table, we have a chore that periodically consumes all of the expired orders in it and inserts them into the existing rollups tables. this is as if we changed the nodes to report as the order expired rather than as soon as possible, so the belief in correctness of the refactor is higher. since we are able to process large batches of orders (typically a day's worth), we can use the code to maximally batch inserts into the rollup tables to make inserts as friendly as possible to cockroach. Change-Id: I25d609ca2679b8331979184f16c6d46d4f74c1a6 |
||
|---|---|---|
| .. | ||
| reports | ||
| api.go | ||
| Dockerfile | ||
| entrypoint | ||
| gracefulexit.go | ||
| main.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