RGW lifecycle not expiring objects due to permissions on lc pool
#1 Updated by Matt Benjamin over 2 years ago
Some notes (cribbed from email by Dan Gryniewicz):
The lifecycle config looks sane; Dan, do you see anything here?
objects are checked for expiration once per day. The start time for processing is configured by "rgw lifecycle work time", and defaults to midnight.
For the record, if you are just testing, we introduced a debug harness (used in Teuthology) that will make each "day" pass in a configurable number of seconds. This should not be used in any production setup, since the overhead can be quite high, but it can be used to avoid waiting a whole day when testing the feature. The configurable is "rgw lc debug interval"
#3 Updated by Yehuda Sadeh about 2 years ago
- Subject changed from RGW lifecycle not expiring objects to RGW lifecycle not expiring objects due to permissions on lc pool
Need to make sure that we log errors, so that these problems are not just silently hidden.