Closed
Bug 737267
Opened 13 years ago
Closed 13 years ago
make reports_clean_done() (and SPs that call it) error checks more configurable
Categories
(Socorro :: Database, task)
Socorro
Database
Tracking
(Not tracked)
RESOLVED
FIXED
24
People
(Reporter: rhelmer, Assigned: selenamarie)
References
Details
(Whiteboard: [qa-])
Per bug 737135 one of the big stumbling blocks to setting up a brand-new Socorro instance is that the stored procedures that drive reports (such as TCBS) do a sanity/error check to make sure that reports_clean has data in the final UTC hour. If this is not the case than the reports fail to run.
This is not appropriate for many installs. We know of people using Socorro who may just get a few crashes per day, let alone per hour.
We should make this configurable - the most obvious place to do that seems to be in the top-level Socorro configuration, which will pass arguments to the SPs to do the right thing.
Comment 1•13 years ago
|
||
basically, we should have a socorro configuration variable called something like "reports_clean_check_time" which defaults to "1 hour", but could be "6 hours" or "1 day" or any valid interval up to 1 day.
This would be passed to each cronjob procedure. This also probably means that we want to switch to using named parameter format for the procedure calls. So it would change from:
select update_tcbs('2012-03-24')
to:
select update_tcbs( updateday := '2012-03-24', check_time := '1 hour' )
... in order to cope with the other default parameters for that function.
Comment 2•13 years ago
|
||
One more issue: not all daily cronjobs need this parameter. Of course, we could program them to take it anyway and simply ignore it.
Reporter | ||
Updated•13 years ago
|
Assignee: nobody → josh
Target Milestone: --- → 4
Updated•13 years ago
|
Target Milestone: 4 → 5
Updated•13 years ago
|
Target Milestone: 5 → 6
Updated•13 years ago
|
Target Milestone: 6 → 7
Comment 3•13 years ago
|
||
At the in-person meeting yesterday, we revised how this is supposed to work for the new cronjob infratructure, so pushing forward.
Target Milestone: 7 → 9
Comment 4•13 years ago
|
||
Pushing to 10, not done yet. Will have it ready for that.
Blocks: 749019
Target Milestone: 9 → 10
Comment 5•13 years ago
|
||
This is getting pushed back in order do make room for rapid betas.
Target Milestone: 10 → 12
Updated•13 years ago
|
Target Milestone: 12 → 13
Updated•13 years ago
|
Target Milestone: 13 → 14
Comment 7•13 years ago
|
||
So, as of Mobeta, all cron jobs which check reports_clean now take an optional "check period" parameter, which is a time interval. This defaults to "1 hour".
This means that the next step is to tie this to a configuration variable passed via the cronjobber.
Updated•13 years ago
|
Target Milestone: 16 → 18
Comment 8•13 years ago
|
||
This will be partly done in Mobeta, but not completely done; I need to do an audit of all matview cron jobs and make sure they comply.
Target Milestone: 18 → 19
Comment 9•13 years ago
|
||
Bumping to 20, due to other needed mobeta fixes.
Depends on: 781989
Target Milestone: 19 → 20
Comment 10•13 years ago
|
||
Moving to 22 so that Selena can complete this.
Assignee: josh → sdeckelmann
Target Milestone: 20 → 22
Assignee | ||
Updated•13 years ago
|
Target Milestone: 22 → 23
Assignee | ||
Comment 11•13 years ago
|
||
I've audited all the update_* functions for this and added the parameter 'check_period'.
r? https://github.com/mozilla/socorro/pull/878
Assignee | ||
Updated•13 years ago
|
Whiteboard: [qa-]
Assignee | ||
Updated•13 years ago
|
Status: NEW → ASSIGNED
Comment 12•13 years ago
|
||
Commit pushed to master at https://github.com/mozilla/socorro
https://github.com/mozilla/socorro/commit/427ba732b34b58844cf1d0800d1611979da34a35
bug 737267: make check_period configurable in matview functions
Assignee | ||
Updated•13 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•13 years ago
|
Target Milestone: 23 → 24
You need to log in
before you can comment on or make changes to this bug.
Description
•