Closed
Bug 747898
Opened 13 years ago
Closed 13 years ago
Backfill ADU data for April 17 - 21 (and topcrashes /aggregations for April 20)
Categories
(Data & BI Services Team :: DB: MySQL, task)
Data & BI Services Team
DB: MySQL
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: kairo, Assigned: scabral)
Details
It looks like metrics has pushed the raw ADU data for the missed days to Socorro, so we should process those into the aggregated data used for graphs, etc. - that's for April 17 - 21, which are missing the ADU data right now.
Also, https://crash-stats.mozilla.com/daily?p=Firefox&v[]= shows no crashes for April 20, we need to re-run the jobs for this as well.
Laura, this is high priority for CrashKill, we need to check *today* if we can ship a release tomorrow and data from the betas in the last few days is paramount for that.
Comment 1•13 years ago
|
||
So we need to do the following:
- Backfill ADU for April 17-21
- Re-run daily and aggregate crons for April 20
Moving over to Server Ops: Databases
Assignee: nobody → server-ops-database
Severity: normal → critical
Component: Database → Server Operations: Database
Product: Socorro → mozilla.org
QA Contact: database → cshields
Version: unspecified → other
Assignee | ||
Comment 2•13 years ago
|
||
breakpad=# select backfill_adu('2012-04-17');
backfill_adu
--------------
t
(1 row)
I'm suspicious because it did not take very long to run this backfill.
Assignee | ||
Comment 3•13 years ago
|
||
Reprocessing matviews for 4/20:
breakpad=# select backfill_matviews('2012-04-20 00:00:00','2012-04-21 00:00:00');
Assignee | ||
Updated•13 years ago
|
Assignee: server-ops-database → scabral
Assignee | ||
Comment 4•13 years ago
|
||
resolving, please re-open if this wasn't actually fixed by the work we did yesterday.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 5•13 years ago
|
||
Thanks, everything looks fine from what I saw.
Status: RESOLVED → VERIFIED
Updated•10 years ago
|
Product: mozilla.org → Data & BI Services Team
You need to log in
before you can comment on or make changes to this bug.
Description
•