7 May
2020
7 May
'20
2:45 p.m.
On Wed, May 6, 2020 at 3:29 AM Katarzyna Myrek <katarzyna(a)myrek.pl> wrote:
Hi
I have a few questions about bucket versioning.
in the output of command "*radosgw-admin bucket stats --bucket=XXX"* there
is info about versions:
"ver": "0#521391,1#516042,2#518098,3#517681,4#518423",
"master_ver": "0#0,1#0,2#0,3#0,4#0",
Also "*metadata get"* returns info about versions:
radosgw-admin metadata get bucket:XXX
{
"key": "bucket:XXX",
"ver": {
"tag": "_KrvQc6gBg1Zcrr8s8M5jXmk",
"ver": 335
},
those fields are all unrelated to s3 bucket versioning
But I'm pretty sure that bucket versioning should
be disabled, because "*aws
s3api get-bucket-versioning*" returns nothing.
How should I understand the current situation?
The problem is that from the client side I can see that the bucket is very
small. Less than 10GB while checking the bucket stats from radosgw-admins
side shows the bucket is taking nearly 1TB.
is it possible that these are incomplete multipart uploads? you can
use the s3api list-multipart-uploads [1] command to list them, and
s3api abort-multipart-upload [2] to reclaim the space for abandoned
uploads. if this is the issue, you might consider automating this
process using bucket lifecycle rules [3]
Kind regards / Pozdrawiam,
Katarzyna Myrek
_______________________________________________
ceph-users mailing list -- ceph-users(a)ceph.io
To unsubscribe send an email to ceph-users-leave(a)ceph.io
[1] https://docs.aws.amazon.com/cli/latest/reference/s3api/list-multipart-uploa…
[2] https://docs.aws.amazon.com/cli/latest/reference/s3api/abort-multipart-uplo…
[3]
https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html#mpu-abort-…