Sharding handoffs creates a *ton* of container-server headers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Related: https:/
From IRC:
<+timburke> NM, why are we worried about [sharded handoff containers]? is it making the account stats flop around or something?
<NM> timburke: not sure if that is the reason but I'm getting some HTTP 503 when I try to list the container content. When I look at my proxy-error I got this message: " ERROR with Container server x.x.x.x:6001/sdb "#012HTTPException: got more than 126 headers"
<NM> If I curl direct to the container-server, it returns 1288 headers of X-Container-
<NM> And they all have the same values: ""max_row": -1, "ranges_todo": 0, "ranges_done": 8, "cleaving_done": true, "last_cleave_
After calling broker.
Bonus points if we can clean up any existing stale contexts -- maybe do something like load all contexts, for each:
if 'last_modified' not in context:
elif context[
and make sure we always update that last modified when saving changes.
Maybe something like the attached patch.
I'll play with it and add some tests and push it up for review in the next day or so.