On 03/27/2017 04:28 PM, ceph.nov...@habmalnefrage.de wrote:
Hi Cephers.
Couldn't find any special documentation about the "S3 object expiration"
so I assume it should work "AWS S3 like" (?!?) ... BUT ...
we have a test cluster based on 11.2.0 - Kraken and I set some object
expiration dates via CyberDuck and DragonDisk, but the objects are still
there, days after the applied date/time. Do I miss something?
Thanks & regards
It is intended to work like AWS S3, yes. Not every feature of AWS
lifecycle is supported, (for example no moving between storage tiers),
but deletion works, and is tested in teuthology runs.
Did you somehow turn it off? The config option rgw_enable_lc_threads
controls it, but it defaults to "on". Also make sure
rgw_lc_debug_interval is not set, and that rgw_lifecycle_work_time isn't
set to some interval too small scan your objects...
Daniel
_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
