Separate node_timeouts per backend-layer
Bug #1834212 reported by
Tim Burke
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Object Storage (swift) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Currently, the proxy uses a single node_timeout when talking to the backend, regardless of which service it's talking to. It'd be nice if operators could separately tune account, container, and object timeouts (potentially with per-policy overrides for the object layer).
This would allow an operator to crank up the container-server timeout to decrease the likelihood of getting bit by https:/
| tags: | added: low-hanging-fruit |
Revision history for this message
| Tim Burke (1-tim-z) wrote | #1 |
To post a comment you must log in.
Also/alternatively: separate timeouts by verb. We often want different timeouts for object PUTs vs object GETs, for example.