https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39314
David Cook <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from David Cook <[email protected]> --- (In reply to Victor Grousset/tuxayo from comment #0) > Reported to Debian as it affects their next release which will do a jump > from 3.10 to 4.0: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100165#10 > > Which can't work: https://www.rabbitmq.com/docs/upgrade > «You can only upgrade to RabbitMQ 4.0 from RabbitMQ 3.13.» That's fun... > For us: is there still data in RabbitMQ when stopping a Koha instance and > upgrading it? I recall reading that the DB was basically mirroring the > message queue data during a discussion about the actual need for a dedicated > message queue. Does it mean the koha-common package can wipe the RabbitMQ > data which will allow it to start without issue? The DB stores the jobs, and the Koha app passes messages to background workers via RabbitMQ. If the background worker starts up and can't get a connection to RabbitMQ, it'll query the DB directly for the jobs. What this means is that if you stopped koha-common, nuked RabbitMQ, re-installed RabbitMQ, and started koha-common, you could have data loss if there were any messages in RabbitMQ that hadn't been processed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
