Closed
Bug 1603663
Opened 5 years ago
Closed 4 years ago
expire cron_log entries older than 6 months
Categories
(Socorro :: General, task, P3)
Socorro
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: willkg, Assigned: willkg)
Details
Attachments
(1 file)
We should expire cron_log entries older than 6 months. We don't need more than 6 months of those kinds of logs and this prevents the table from growing unbounded.
We could do this in the cronrun command or add another command to expire logs. The latter is probably easier.
|
Assignee | |
Comment 1•4 years ago
|
||
We should just write a cron job to do it.
Grabbing this to do soon.
Assignee: nobody → willkg
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 2•4 years ago
|
||
|
|
Assignee | |
Comment 3•4 years ago
|
||
|
|
Assignee | |
Comment 4•4 years ago
|
||
When this deploys to stage, I'll verify it there.
Stage has 52,191 (or so) log entries now dating back to October 2018. This should whack all but the last six months.
|
|
Assignee | |
Comment 5•4 years ago
|
||
cleanse_cronlog ran on stage early this morning. Stage now has 13,545 log entries dating back to March 7th, 2020. Perfect!
|
|
Assignee | |
Comment 6•4 years ago
|
||
I pushed the latest changes to prod in bug #1664250. Marking as FIXED.
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•