Closed
Bug 1275889
Opened 9 years ago
Closed 9 years ago
Deploy / backfill main_summary v3
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mreid, Assigned: mreid)
References
Details
Attachments
(3 files)
Now that the code has been refactored and tested, the data needs to be backfilled.
Assignee | ||
Comment 1•9 years ago
|
||
Any new fields should be added before backfilling.
Assignee: nobody → mreid
Points: --- → 2
Priority: -- → P1
Assignee | ||
Updated•9 years ago
|
Assignee | ||
Comment 2•9 years ago
|
||
Deployment is done. Backfill still remains.
Assignee | ||
Comment 3•9 years ago
|
||
Backfill will need to take into account the update in bug 1286262 and the outage in bug 1286226
Blocks: 1286226
Comment 5•9 years ago
|
||
Assignee | ||
Comment 6•9 years ago
|
||
(In reply to Sam Penrose from comment #4)
> Do we have an ETA on this?
I'm planning to kick off the backfill proper once we know that it won't overwhelm the system. The PR above sets it to run a max of 10 days of backfill at once, so that should leave some capacity for all the other jobs.
Once the jobs are all running, I expect it will take a few days to complete.
Flags: needinfo?(mreid)
Assignee | ||
Updated•9 years ago
|
Attachment #8775127 -
Flags: review?(rvitillo)
Updated•9 years ago
|
Attachment #8775127 -
Flags: review?(rvitillo) → review+
Comment 7•9 years ago
|
||
Comment 8•9 years ago
|
||
Assignee | ||
Comment 9•9 years ago
|
||
After a fair amount of debugging with Airflow's backfill capability, a backfill-specific version of the DAG is now running, namely the one added in the PR from comment 8.
It will be backfilled for 180 days of history (back to 2016-03-12) per the usual retention period.
Assignee | ||
Comment 10•9 years ago
|
||
Backfill has completed.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•