Since introducing reports_clean in 2.3.2, the auditing table, reports_bad, has grown to 600MB. This needs to be trimmed. Current plan is to update the update_reports_clean to trim it down to 2 days.
Completed and pushed to -dev for testing for 2.3.4
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Target Milestone: 2.4 → 2.3.4
What are the steps for qa or can this be marked [qa-]?
reports_bad is an internal auditing table with no UI. so I think it's [qa-]
Status: RESOLVED → VERIFIED
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.