Hi,
When uploading to RGW via swift I can set an expiration time. The files being uploaded are large. We segment them using the swift upload ‘-S’ arg. This results in a 0-byte file in the bucket and all the
data frags landing in a *_segments bucket.
When the expiration passes the 0-byte file is delete but all the segments remain. Am I misconfigured or is this a bug where it won’t expire the actual data? Shouldn’t RGW set the expiration on the uploaded
segments too if they’re managed separately?
Thanks,
peter
| Peter Eisch | | Senior Site Reliability Engineer |
|
| | | | Australia | Bosnia and Herzegovina | Brazil | Canada | Singapore | Switzerland | United Kingdom | USA
|
| | Confidentiality Notice: The information contained in this e-mail, including any attachment(s), is intended solely for use by the designated recipient(s). Unauthorized use, dissemination, distribution, or reproduction of this message by anyone other than the intended recipient(s), or a person designated as responsible for delivering such messages to the intended recipient, is strictly prohibited and may be unlawful. This e-mail may contain proprietary, confidential or privileged information. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Virgin Pulse, Inc. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this e-mail message. |
|
| |
|
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
