Closed Bug 1368378 Opened 7 years ago Closed 7 years ago

blobber expiration policies aren't working

Categories

(Release Engineering :: General, enhancement, P1)

Product:
Release Engineering
Component:
General
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: nthomas, Assigned: nthomas)

Details

The S3 console says we have about 95TB of data in mozilla-releng-blobs, the bucket for the blobber service. There are a 40+ lifecycle policies for specific directories, going back to esr24 and including mozilla-inbound but not autoland, which want to remove blobs after 30 days. They don't seem to be working though. 

They all specify prefixes like '/blobs/mozilla-inbound/' which are valid except for possibly the leading /. I'm testing removing that for Birch.

Since there is no special treatment for any branch (they all set 30 days) so it makes more sense to have a zero-maintenance policy which affects 'blobs/'. Any objections Rail ?
Flags: needinfo?(rail)
Sheriffs, do you know of any fallout of fixing this accidental infinite-retention in blobber ?
Wow, it sounds like a lot! Sounds like it'd be better to keep those under control. Let's do it!
Flags: needinfo?(rail)
I've set a 90-day expiry for initial cleanup.
That dropped us ~80TB to 14.6TB over 1.8M objects. I'll take an 85% reduction which still retains some utility for people going back to older builds.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.