A recent survey on IRC revealed that a lot of people are still running Koha without RabbitMQ. It's not a small dependency and for smaller libraries it might not be needed ever. Also we still see issues with jobs not being processed correctly that has people turning it off. We should not create any warns or logs, but have a proper switch to turn RabbitMQ off without Koha complaining until we can fully rely on RabbitMQ at least.
+1 We have turned RabbitMQ off on a lot of sites, because things work better without it.
See the discussion on 35092. And the several options suggested. Your feedback is appreciated.
(In reply to Marcel de Rooy from comment #2) > See the discussion on 35092. And the several options suggested. Your > feedback is appreciated. Thanks Marcel, for pointing this one out. I am all for fixing the remaining issues, but I feel we need a solution for stable installations until and I also see a use case for very small installations as RabbitMQ is taking additional resources.
I just ran into problems with background jobs again (koha-common/stable,now 23.11.04-4 all [installed]) There has been a discussion regarding RabbitMQ at the workshop in Marseille. I still think we would be better off without rabbitMQ. + no parallel solution (DBpoll+rabbitmq) + no extra service that has to be maintained (sysop) and i dont see the benefits rabbitmq brings. if i knew for sure the DB poll mechanism is here to stay i would love to have a config param to disable rabbitmq. and not have debian pull in the rabbitmq dependency.
(In reply to davewood from comment #4) Thx for your feedback. See also bug 35092. > I just ran into problems with background jobs again (koha-common/stable,now > 23.11.04-4 all [installed]) Could you provide some more details here? What are those problems? Are they related to insufficient resources? Or ... ?