[Koha-bugs] [Bug 33044] BackgroundJob enqueue does not return the job id if rabbit is unreachable

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

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

Marcel de Rooy <m.de.rooy at rijksmuseum.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dcook at prosentient.com.au,
                   |                            |jonathan.druart+koha at gmail.
                   |                            |com,
                   |                            |katrin.fischer at bsz-bw.de,
                   |                            |kyle at bywatersolutions.com,
                   |                            |martin.renvoize at ptfs-europe
                   |                            |.com, tomascohen at gmail.com
             Status|BLOCKED                     |Passed QA

--- Comment #5 from Marcel de Rooy <m.de.rooy at rijksmuseum.nl> ---
The patch is simple and works.
But I feel that we are on the crossroad here: Should we facilitate working
without rabbitmq any further?

Should we put more time in getting it stable in Koha? Is the plugin we use the
cause of that? Bad configuration? Many people run it and it should be able to
handle millions of messages.. The volume of messages in Koha is not expected to
be that large.

The hybrid solution for background jobs feels like 'suboptimal' design to me.
The current state allows for strange sync issues: you can submit jobs without
rabbitmq; if the worker is running and rabbit is not, they will be picked up.
If the worker was not running, and you restart rabbit and worker, these jobs
will be ignored since they are not in rabbit.

PQA could have been In discussion too :)

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