Closed
Bug 754461
Opened 13 years ago
Closed 13 years ago
Setup automated data refresh for crash-stats-dev
Categories
(Socorro :: Database, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jberkus, Assigned: mpressman)
References
Details
(Whiteboard: [stageDB setup])
Set up weekly automated database refresh for crash-stats-dev.
Will refresh using 4 weeks of data from ReplayDB
Will use miniDB scripts.
Refresh should be on Saturday nights.
Once supporting scripts are available, refresh should automatically pull in any database changes.
| Reporter | ||
Updated•13 years ago
|
Whiteboard: [stageDB setup]
| Assignee | ||
Comment 1•13 years ago
|
||
I have the script ready to go and will verify it's running tomorrow night
| Assignee | ||
Comment 2•13 years ago
|
||
since the replaydb storage location has been requested to be moved, this will not be verified as fully working until it can run automatically next Saturday to the new machine.
| Assignee | ||
Comment 3•13 years ago
|
||
This script will be verified, but will not be considered completed until it runs automated with the newly setup environment now that replaydb is on the devdb instance.
| Assignee | ||
Comment 4•13 years ago
|
||
Because the script didn't run without errors last Saturday, I've been working out the kinks, notably emailing errors rather than the errors that went to stdout. Additionally, I need to get this into puppet. Fingers crossed, this Saturday, the 26th should have a successful run and this will be completed. There is also a question about coordinating this with the backups running on from the replicated instance on devdb in bug 682284
| Assignee | ||
Comment 5•13 years ago
|
||
The c-s-d automated refresh is complete. It successfully runs and takes on average 30 minutes.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•