unlink_older_than should not use reclaim_age

Bug #1691565 reported by clayg on 2017-05-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Object Storage (swift)
Undecided
Unassigned

Bug Description

Reclaim age is a very specific tunable that has to do with cleaning up tombstone entries and should be tied to not only your consistency engine cycle time - but also the age at which you can safely re-introduce hardware that has been out of the cluster. It is *very* long.

The same value is also in-explicably used to determine how long to wait before reaping temporary files - generally the default reclaim age is much too long - and specifically it's not in anyway related to tombstone reaping.

The time window/value used with unlink_older_than in the db/object-replciator should be a separate tunable from reclaim age - and also much lower.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers