[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 #17 from Tomás Cohen Arazi <tomascohen at gmail.com> ---
(In reply to Tomás Cohen Arazi from comment #11)
> (In reply to David Cook from comment #8)
> > 
> > RabbitMQ isn't the wrong tool for the job
> 
> The question is: are we better with just polling? What do we lose?

I didn't intend to restart this conversation. Just to start over on which
benefits it offers and why we should go full MQ. I think we never entirely
implement it correctly.

Regarding the ack discussion, it feels to me that many of our problems are
related to the 'ack last' behavior. As you said, we have our own way of
tracking progress and termination, so we are safe to just ack and leave that to
Koha.

I've been pondering having separate workers for polling and rabbit
respectively. It would simplify things a lot.

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