View Issue Details

IDProjectCategoryView StatusLast Update
5586Composrcorepublic2024-07-23 15:03
ReporterPDStig Assigned ToPDStig  
PrioritynormalSeverityfeature 
Status assignedResolutionopen 
Summary5586: Task queue: Cron does not respect number of locked tasks; maybe it should
DescriptionIt is possible for a server to get overloaded with multiple tasks running at the same time. This is because Cron will start a new task from the queue regardless of the number of tasks locked.

Perhaps this behaviour should be modified. Maybe Cron should not start a new task if X tasks are currently locked, or maybe base it off of whether or not we are in failsafe or if (using the same criteria as the health check) resource use is high.
Additional InformationActually Cron loads up all of them at the same time. Maybe we should also limit this to X tasks per Cron execution. Though, if all of them are loaded up in one Cron, that means only one thread is dedicated to running all of the tasks, which may be okay until / unless we get more tasks queued between each Cron run.
TagsRoadmap: Over the horizon
Attach Tags
Time estimation (hours)
Sponsorship open

Sponsor

Date Added Member Amount Sponsored

Relationships

related to 5656 ResolvedPDStig Optimise task queue more intelligently 

Activities

PDStig

2024-01-31 03:22

administrator   ~8281

We will also need a health check for making sure the task queue is not stuck.

PDStig

2024-03-30 14:59

administrator   ~8499

I'm keeping this as something we should consider for 11.0. This is because delete members and privacy purging are now background tasks, which both can be very intense processes if done on a mass amount of data. Therefore it makes this consideration more vital.

PDStig

2024-04-12 20:17

administrator   ~8580

Not as important now that the task queue was optimized in v11 alpha2. Changed to over the horizon.

Add Note

View Status
Note
Upload Files
Maximum size: 32,768 KiB

Attach files by dragging & dropping, selecting or pasting them.
You are not logged in You are not logged in. This means you will not get any e-mail notifications. And if you reply, we will not know for sure you are the original poster of the issue.

Issue History

Date Modified Username Field Change
2024-01-31 03:14 PDStig New Issue
2024-01-31 03:14 PDStig Status Not Assigned => Assigned
2024-01-31 03:14 PDStig Assigned To => user4172
2024-01-31 03:14 PDStig Tag Attached: Roadmap: v11
2024-01-31 03:17 PDStig Additional Information Updated
2024-01-31 03:22 PDStig Note Added: 0008281
2024-03-30 14:58 PDStig Severity Minor Bug => Feature or Request
2024-03-30 14:59 PDStig Note Added: 0008499
2024-04-12 20:17 PDStig Tag Detached: Roadmap: v11
2024-04-12 20:17 PDStig Tag Attached: Roadmap: Over the horizon
2024-04-12 20:17 PDStig Note Added: 0008580
2024-07-23 15:03 Chris Graham Relationship added related to 5656