Object DELETE returning 503 for (404, 204)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
- Swift structure Account: 3Copy Container: 3Copy Object: 2Copy (2 replicas)
- Swift version: icehouse
- Issue: Object DELETE returning 503 for (404, 204)
When deleting from Swift, proxy.error will result in the following error: Object DELETE returning 503 for (404, 204)
Object delete DELETE returning 503 for (404, 204) error when executing delete When restarting the proxy server daemon, the deletion is normal again.
By the way, restarting proxy server daemon, swift daemon is not deleted at present.
If you delete the files in the container and check for an error 503, The file with the error has not been deleted already. Again, when the client executes the deletion, it will repeatedly stop the deletion with a 503 error.
Container access to the database I checked the object file in the container for the actual 503 error. I looked up each field value Size: 0, etag: deleted, deleted: 1. Compared to other files that have not been deleted, the values of the above fields are incorrect, and even if a 503 error occurs, it appears to have been deleted.
Again, swift-get-nodes queries the disk for the existence of the deleted data. The object file does not exist.
Of course, the above method has been successfully executed without any abnormality (even if a 503 error occurs during the deletion, when the proxy daemon is restarted, the deletion is normally performed again).
There is no change in the method of deletion.
Object DELETE returning 503 for (404, 204) I want to solve.
summary: |
- Object DELETE returning 503 for (404, 204) + (404, 204)에 대해 503을 반환하는 객체 DELETE |
description: | updated |
description: | updated |
summary: |
- (404, 204)에 대해 503을 반환하는 객체 DELETE + Object DELETE returning 503 for (404, 204) |
Changed in swift: | |
assignee: | nobody → hwang, sungi (sungiing) |
assignee: | hwang, sungi (sungiing) → nobody |
description: | updated |
For 2-replica policies this should have been fixed with f4d3facd [1]
Can you test with master and confirm?
I'm showing that as being in swift since 2.2
Icehouse was EOL Apr 17, 2014
1. https:/ /review. openstack. org/#/c/ 114120/