Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.3.0-b1
-
Fix Version/s: 4.3.0
-
Component/s: None
-
Labels:None
Description
Cron tasks that take a long time to run can overlap and be re-run. For example, if a cron task runs every 5 minutes, but takes 6 minutes to complete, will attempt to be run a second time before the first one has finished.
We prevent this behavior of re-running a currently-running task by making sure it has completed running before starting a new instance. For some cron tasks, however, logging information sets the task end date, which marks it completed and open to be run again.
- Fix the cron so that tasks are not marked completed unless and until they are
Activity
Tyson Phillips (Inactive)
created issue -
Tyson Phillips (Inactive)
made changes -
Field | Original Value | New Value |
---|---|---|
Rank | Ranked higher |
Tyson Phillips (Inactive)
made changes -
Sprint | 4.3.0 Sprint 12 [ 63 ] |
Tyson Phillips (Inactive)
made changes -
Rank | Ranked higher |
Automated transition triggered when Tyson Phillips (Inactive) created a branch in Stash -
Status | Open [ 1 ] | In Progress [ 3 ] |
Automated transition triggered when Tyson Phillips (Inactive) created pull request #485 in Stash -
Status | In Progress [ 3 ] | In Review [ 5 ] |
Resolution | Fixed [ 1 ] |
Tyson Phillips (Inactive)
made changes -
Remaining Estimate | 0 minutes [ 0 ] | |
Time Spent | 1 hour, 50 minutes [ 6600 ] | |
Worklog Id | 11350 [ 11350 ] |
Tyson Phillips (Inactive)
made changes -
Time Spent | 1 hour, 50 minutes [ 6600 ] | 1 hour, 58 minutes [ 7080 ] |
Worklog Id | 11352 [ 11352 ] |
Automated transition triggered when Tyson Phillips (Inactive) merged pull request #485 in Stash -
Status | In Review [ 5 ] | Closed [ 6 ] |