Closed Bug 596766 Opened 14 years ago Closed 14 years ago

Disable crons and clear out bad aggregate data

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

All
Other
task
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ozten, Assigned: aravind)

Details

Last night's release has corrupted the crash signatures in the reports and top crashers by signature view for window of time.

Metrics is rebuilding out backend view which will fix these entries in the reports table.

We need to disable the crons and then remove the bad entries.

Steps:
1) remove startTopCrashersBySignature.py from the crontab
2) Excute the following SQL
DELETE FROM top_crashes_by_signature WHERE window_end > '2010-09-14 12:00';
Assignee: server-ops → aravind
In staging

breakpad=> DELETE FROM top_crashes_by_signature WHERE window_end > '2010-09-14 12:00';
DELETE 0
breakpad=> 

Is that expected, okay to run it in production?
(In reply to comment #1)
Okay. Please run in prod.
breakpad=> DELETE FROM top_crashes_by_signature WHERE window_end > '2010-09-14 12:00';
DELETE 107702
breakpad=> \q


Cron job commented out.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Seeing this right now in prod and stage (bug 596881 comment 3 and bug 596881 comment 6).

Do we need to do something like this again?
(In reply to comment #4)
> Seeing this right now in prod and stage (bug 596881 comment 3 and bug 596881
> comment 6).
> 
> Do we need to do something like this again?

That bug is about top crashers by domain, BTW.
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.