[Koha-bugs] [Bug 32573] background_jobs_worker.pl should ACK a message before it forks and runs the job

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32573

--- Comment #5 from Kyle M Hall <kyle at bywatersolutions.com> ---
(In reply to David Cook from comment #4)
> If you were doing a big batch record modification and you suffered a power
> outage on the machine where the background job worker is running, then that
> task can't be re-started since the RabbitMQ message was already ACKed before
> the real work began.
> 
> (Of course, in the case of Koha, we have the "database failover", so in
> theory it might get recovered, but it's not standard design.)

Considering batch record modifications are not atomic, I don't think that's
necessarily a compelling argument.

I can't see any scenario where either:
A) We should ack before processing. We are stymying Koha's ability to do
background processing by running extrememly long processes in serial with no
way to fork multiple background jobs at one.

B) RabbitMQ/STOMP is the wrong tool for the job and we should remove it's use
from Koha.

-- 
You are receiving this mail because:
You are watching all bug changes.