Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delete large object #117

Open
protheusfr opened this issue Sep 8, 2016 · 1 comment
Open

Delete large object #117

protheusfr opened this issue Sep 8, 2016 · 1 comment

Comments

@protheusfr
Copy link

protheusfr commented Sep 8, 2016

Hello,

I have an issue when I call object.delete() on a large object (~10GB).
During the upload, the large object is well segmented in smaller file (5GB each on server), and I obtain something like that in the container :
10GB.file 10GB.file/00000001 10GB.file/00000002 10GB.file/00000003

But after .delete() call, only the first file (10GB.file) is really deleted.
The "real" data remain on server.

(Tested with V0.9.12 & V0.9.13 and a Ceph infrastructure as backend)

I've looked for a special call to delete large object but it seems it is automatically managed by the interface.

Do I something wrong ?

@protheusfr
Copy link
Author

Additional infos, when I get the obkect metadata (via a HTTP HEAD command) I obtain the following data :

HTTP/1.1 200 OK Content-Length: 0 Accept-Ranges: bytes Last-Modified: Tue, 13 Sep 2016 13:36:29 GMT X-Timestamp: 1473773789.50871 etag: d41d8cd98f00b204e9800998ecf8427e X-Object-Manifest: images2/10GB.file X-Delete-At: 1481549789 X-Trans-Id: tx0000000000000000001c7-0057d80156-32600-dc1-qual Content-Type: # Date: Tue, 13 Sep 2016 13:38:30 GMT

It seem it miss the X-Static-Large-Object that indicate this is a large object (even if it is stored as a large object :

capture d ecran 2016-09-13 a 15 41 20

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant