Ask Your Question

500 exception on upload

asked 2013-09-12 17:27:00 -0500

David Loy gravatar image

updated 2016-12-22 23:13:41 -0500

fifieldt gravatar image

The private rackspace cloud we are using issues a 500 exception on an upload request if the content is not written to both the primary and backup nodes. The primary write actually happens with the 500 and the backup write is automatically performed on this system when the failed backup node come back online.

We were assured that the 500 is OK because 1/2 of the writes are completed. Is this the standard behavior for openstack? How can we distinguish between a 1/2 write and a total system failure with a single 500? Rereading the uploaded content is not the preferred mechanism because some content is in the 1G range. It's not conclusive but it looks like a HEAD request returns a 503 when hitting this content.

Any suggestions for handling this problem as a client or as a rackspace manager would be wonderful.

Thanks David

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2016-12-22 23:17:04 -0500

fifieldt gravatar image

A successful upload to swift (denoted by creating enough replicas to beat the quorum requirement) will return Created (201). If you are seeing a 500, it indicates an error with your install.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2013-09-12 17:27:00 -0500

Seen: 110 times

Last updated: Dec 22 '16