Closed
Bug 1038234
Opened 10 years ago
Closed 10 years ago
[prod] crontabber trying to rerun signature summary matviews after backfill
Categories
(Socorro :: Database, task)
Socorro
Database
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rhelmer, Assigned: rhelmer)
Details
Yesterday there was a manual backfill (bug 1037960) and today most things recovered, except for the "signature summary" related stored procedures: https://errormill.mozilla.org/webtools/socorro-prod/group/169290/ DETAIL: Key (report_date, product_version_id, signature_id, android_device_id)=(2014-07-12, 2338, 5836041, 84165) already exists. It looks like the SP is not detecting that it was already run and returning "false", which would cause crontabber to handle this like it did for other things. To recover I think we'll need to: * reset these jobs so crontabber gives up on them * manually backfill I'll get started on this.
Assignee | ||
Comment 1•10 years ago
|
||
Reset jobs: for job in signature-summary-uptime-process-type signature-summary-products-matview signature-summary-uptime-os signature-summary-uptime-architecture signature-summary-uptime-flash-version signature-summary-uptime-matview signature-summary-installations-matview signature-summary-uptime-device; do $PYTHON socorro/cron/crontabber_app.py --reset $job; done
Assignee | ||
Comment 2•10 years ago
|
||
There don't seem to be backfill functions for each of these.. going to do a regular backfill (skipping reports_clean): breakpad=# select backfill_matviews('2014-07-13', '2014-07-13', False);
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•10 years ago
|
||
Crontabber had already run these so backfill turned out to be unnecessary - just resetting the jobs was enough.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•