Bug 41245 - Add ability to limit background workers by job type
Summary: Add ability to limit background workers by job type
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Architecture, internals, and plumbing (show other bugs)
Version: 25.05
Hardware: All All
: P5 - low enhancement
Assignee: Kyle M Hall (khall)
QA Contact: Testopia
URL:
Keywords:
: 34138 (view as bug list)
Depends on:
Blocks:
 
Reported: 2025-11-13 13:09 UTC by Kyle M Hall (khall)
Modified: 2025-11-13 14:37 UTC (History)
2 users (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments
Bug 41245: Add ability to limit background workers by job type (12.27 KB, patch)
2025-11-13 13:16 UTC, Kyle M Hall (khall)
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Kyle M Hall (khall) 2025-11-13 13:09:33 UTC
In practice, some job types can cause other job types to get "backed up". It wouuld be good to be able to specify background job workers for specific job types.
Comment 1 Kyle M Hall (khall) 2025-11-13 13:16:01 UTC
Created attachment 189558 [details] [review]
Bug 41245: Add ability to limit background workers by job type

In practice, some job types can cause other job types to get "backed up".
It wouuld be good to be able to specify background job workers for specific job types.

Test plan:
1) Apply this patch
2) Stop all background jobs
3) Ensure there are new jobs for at least 2 job types
4) Run background_jobs_worker.pl with --type
5) Verify the type of job specified is the only one not processed
6) Stop the worker
7) Qeueue some new jobs of that type
8) Run background_jobs_worker.pl with --not-type
9) Verify the type of job specified is the only one *not* processed
Comment 2 Kyle M Hall (khall) 2025-11-13 14:37:53 UTC
*** Bug 34138 has been marked as a duplicate of this bug. ***