From: WeiGuo Ren <rwg1335252904@gmail.com>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: rgw: In a multi-site environment, deleting the key from the bucket list operation will cause the object's key to be permanently lost.
Date: Thu, 8 Apr 2021 10:09:14 +0800 [thread overview]
Message-ID: <CAPy+zYWq6zUq0OV=ob=NnV1h1tUqG9BnQGSsyJ99gDrFCPMFmQ@mail.gmail.com> (raw)
In a multi-site synchronization environment, the bucket full sync
process will send a bucket list request to the remote, but the remote
execution of the bucket list operation is likely to delete the object
key.
for example:
t1 object upload-start [rgw_bucket_dir_entry.exists =false] (put obj)
t2 list bucket opreate start find 'rgw_bucket_dir_entry.exists
=false',and get_obj_state() return noevent. (list bucket)
t3 object upload-end ,[rgw_bucket_dir_entry.exists =true],(put obj)
t4 list bucket remove object key because t2.(list bucket)
I wonder if it is possible to add a timestamp to rgw_bucket_dir_entry,
if you want to delete the key, to determine whether it expires and
delete it.
reply other threads:[~2021-04-08 2:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPy+zYWq6zUq0OV=ob=NnV1h1tUqG9BnQGSsyJ99gDrFCPMFmQ@mail.gmail.com' \
--to=rwg1335252904@gmail.com \
--cc=ceph-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).