[Koha-bugs] [Bug 32481] Rabbit times out when too many jobs are queued and the response takes too long

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

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

David Cook <dcook at prosentient.com.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dcook at prosentient.com.au

--- Comment #3 from David Cook <dcook at prosentient.com.au> ---
(In reply to Katrin Fischer from comment #2)
> I am slightly confused by this one, wasn't the idea of RabbitMQ to avoid
> just this kind of thing? Having a server dealing with the jobs so nothing
> would be lost and it all done in due time? It seems strange that we run into
> limitations so soon.

Generally speaking, Koha developers are not experienced with using advanced
tools and techniques. Even the most hardcore of Koha developers are still just
beginners with things like distributed computing. 

According to the RabbitMQ Work Queues tutorial, we're doing the right thing by
ACKing after the message has been processed.

I think options would be increasing the timeout, or changing how we're
enqueuing tasks.

In this case, are the "6 batch modifications" actually 1 batch modification job
for 6 items? Why were they taking 6 minutes?

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