container-sharder has no latch when reporting stats
Bug #1834097 reported by
Tim Burke
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
In the container updater, we track our last-reported timestamps, objects, and bytes used and only send the update if something changed: https:/
This helps prevent the account server from getting overloaded trying to write down a bunch of information it already knows.
The sharder doesn't have any of these guards; as a result, if a root container has 1,000 shards, it'll be trying to eat 3,000 updates every sharder cycle. We should add similar protections for the sharder.
To post a comment you must log in.
Fix proposed: https:/ /review. opendev. org/#/c/ 675014/