Public bug reported:
The proxy server during object puts where a write timeout to an object
server will catch the exception, log it, and then proceed to send the
next chunk to that object server later. This behavior can cause the
object server to return an odd etag causing a 422 later from the proxy.
We should close that object server connection on a write timeout and
return a 5xx when we have too few connections left (< replicas / 2).
** Affects: swift
Importance: Undecided
Status: New
--
Write timeout bug in proxy server
https://bugs.launchpad.net/bugs/651598
You received this bug notification because you are a member of Registry
Administrators, which is subscribed to OpenStack Object Storage (swift).
_______________________________________________
Mailing list: https://launchpad.net/~registry
Post to : [email protected]
Unsubscribe : https://launchpad.net/~registry
More help : https://help.launchpad.net/ListHelp
