15508d270c
For bucket_bandwidth_rollups we are trying to insert lots of entries with empty bucket name and project id. Those are inserts from orders created by repair, audit and GE. High load on the same primary key (the same range) is causing many retries and that's affect all inserts as we are putting 1000 entries into DB a once. This change solves this problem by not storing into bucket_bandwidth_rollups other actions then GET and PUT. Those actions are only important from bucket bandwidth usage perspective because those are actions performed by users. Other actions (repair, audit or GE) are also stored in storagenode_bandwdith_rollups so we will still have access to them e.g. for statistic purposes. https://github.com/storj/storj/issues/5332 Change-Id: Ibb5bf0a4c869b0439dc65da1c9342a38ca2890ba |
||
|---|---|---|
| .. | ||
| encryptionkey_test.go | ||
| encryptionkey.go | ||
| endpoint_test.go | ||
| endpoint.go | ||
| orders_test.go | ||
| rollups_chore.go | ||
| rollups_write_cache_test.go | ||
| rollups_write_cache.go | ||
| service_test.go | ||
| service.go | ||
| signer_test.go | ||
| signer.go | ||
| window_endpoint_phase.go | ||