Have you opened a ceph tracker issue, so that we don't lose track of the problem? Thanks, Yehuda On Fri, Jun 2, 2017 at 3:05 PM, <ceph.novice@xxxxxxxxxxxxxxxx> wrote: > Hi Graham. > > We are on Kraken and have the same problem with "lifecycle". Various (other) tools like s3cmd or CyberDuck do show the applied "expiration" settings, but objects seem never to be purged. > > If you should have new findings, hints,... PLEASE share/let me know. > > Thanks a lot! > Anton > > > Gesendet: Freitag, 19. Mai 2017 um 22:44 Uhr > Von: "Graham Allan" <gta@xxxxxxx> > An: ceph-users@xxxxxxxxxxxxxx > Betreff: RGW lifecycle not expiring objects > I've been having a hard time getting the s3 object lifecycle to do > anything here. I was able to set a lifecycle on a test bucket. As others > also seem to have found, I do get an EACCES error on setting the > lifecycle, but it does however get stored: > >> % aws --endpoint-url https://xxx.xxx.xxx.xxx s3api get-bucket-lifecycle-configuration --bucket=testgta >> { >> "Rules": [ >> { >> "Status": "Enabled", >> "Prefix": "", >> "Expiration": { >> "Days": 3 >> }, >> "ID": "test" >> } >> ] >> } > > but many days later I have yet to see any object actually get expired. > There are some hints in the rgw log that the expiry thread does run > periodically: > >> 2017-05-19 03:49:03.281347 7f74f1134700 2 RGWDataChangesLog::ChangesRenewThread: start >> 2017-05-19 03:49:16.356022 7f74ef931700 2 object expiration: start >> 2017-05-19 03:49:16.356036 7f74ef931700 20 proceeding shard = obj_delete_at_hint.0000000000 >> 2017-05-19 03:49:16.359785 7f74ef931700 20 proceeding shard = obj_delete_at_hint.0000000001 >> 2017-05-19 03:49:16.364667 7f74ef931700 20 proceeding shard = obj_delete_at_hint.0000000002 >> 2017-05-19 03:49:16.369636 7f74ef931700 20 proceeding shard = obj_delete_at_hint.0000000003 > ... >> 2017-05-19 03:49:16.803270 7f74ef931700 20 proceeding shard = obj_delete_at_hint.0000000126 >> 2017-05-19 03:49:16.806423 7f74ef931700 2 object expiration: stop > > "radosgw-admin lc process" gives me no output unless I enable debug, then: > >> ]# radosgw-admin lc process >> 2017-05-19 15:28:46.383049 7fedb9ffb700 2 RGWDataChangesLog::ChangesRenewThread: start >> 2017-05-19 15:28:46.421806 7feddc240c80 10 Cannot find current period zone using local zone >> 2017-05-19 15:28:46.453431 7feddc240c80 2 all 8 watchers are set, enabling cache >> 2017-05-19 15:28:46.614991 7feddc240c80 2 removed watcher, disabling cache > > "radosgw-admin lc list" seems to return "empty" output: > >> # radosgw-admin lc list >> [] > > Is there anything obvious that I might be missing? > > Graham > -- > Graham Allan > Minnesota Supercomputing Institute - gta@xxxxxxx > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com[http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com] > > > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |