Lifecycle is designed to run once per day. There's a lot of resource
optimization that's done based on this assumption to reduce the overhead
of lifecycle on the cluster. One of these is that it only builds the
list of objects to handle the first time it's run in that day. So, in
this case, you ran it manually, and it built the list of objects, and
processed them. The next time you run it the same day, it processes the
same list, finds nothing to do, and exits. Objects added since the
lifecycle run for the day was started will be processed the next day.
Daniel
On 2/26/20 7:18 AM, quexian da wrote:
ceph version 14.2.5 (ad5bd132e1492173c85fda2cc863152730b16a92) nautilus
(stable)
I made a bucket named "test_lc" and ran `s3cmd expire
--expiry-date=2019-01-01 s3://test_lc` to set the lifecycle (2019-01-01 is
earlier than current date so every object will be removed).
Then I ran `radosgw-admin lc process`, the objects got deleted as expected,
and the status from `radosgw-admin lc list` is "completed". However, if I
upload some objects, and ran `radosgw-admin lc process` again, the objects
were not deleted.
Could you please tell me what the reason is and what I should do in this
case? Thanks in advance!
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
