Bug 27782 - If a BackgroundJob should fail, it should NOT bring down the worker!
Summary: If a BackgroundJob should fail, it should NOT bring down the worker!
Status: RESOLVED DUPLICATE of bug 27756
Alias: None
Product: Koha
Classification: Unclassified
Component: Architecture, internals, and plumbing (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on: 22417
Blocks:
  Show dependency tree / graph
 
Reported: 2021-02-24 19:42 UTC by Martin Renvoize (ashimema)
Modified: 2021-09-14 16:59 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Renvoize (ashimema) 2021-02-24 19:42:22 UTC 
Our worker does not fork to run tasks, so if a task explodes, the worker it brought down with it... that is bad.
Comment 1 David Cook 2021-02-24 23:35:49 UTC 
(In reply to Martin Renvoize from comment #0)
> Our worker does not fork to run tasks, so if a task explodes, the worker it
> brought down with it... that is bad.

Agreed.

It should be forking. Even if we wrapped the processing in an eval{}, we should still be forking from a memory efficiency perspective.
Comment 2 Jonathan Druart 2021-09-14 16:59:13 UTC 

*** This bug has been marked as a duplicate of bug 27756 ***