Interrupting and re-running recurring reports can cause duplicated schedule entries
Bug #1893463 reported by
Jason Boyer
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.5 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
All supported versions of Evergreen affected
If a problem occurs that interrupts a recurring report but doesn't close the state database connection out from under the reporter it will still go ahead and schedule the next iteration of the report. If you then reset the initial schedule entry to re-run the interrupted report a second entry will be created for the next run when it finishes. This is easily avoided with a unique constraint on a few fields on reporter.schedule.
tags: | added: pullrequest reports |
Changed in evergreen: | |
milestone: | none → 3.6.0 |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Here's a branch that addresses this by adding a unique index on the report, folder, runner, run_time, and email fields of reporter.schedule: https:/ /git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ jboyer/ lp1893463_ uniq_recurrence / working/ user/jboyer/ lp1893463_ uniq_recurrence
Clark is also taught that the specific error caused by this constraint is not a problem.