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

--- Comment #9 from Victor Grousset/tuxayo <[email protected]> ---
On the Debian side, there isn't much they can do without causing other issues.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100165#44
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100165#51

At least there are some strategies:
> Heavy RabbitMQ users that cannot reset their /var/lib/rabbitmq/mnesia 
> database could maybe use upstream docker image to attempt a rolling 
> upgrade. Otherwise, users are advised to simply drain all queues and 
> make clients point to a new cluster if that's possible.

At least the Debian release notes should warn about this:
> writing about it in the Trixie release notes

I don't know about Ubuntu.
And whether that's enough anyway.

Should we put a note on the release notes of Bug 41077?
Wait, that wouldn't work since there is no patch. Same if we put something in
the release notes here.
Any ideas?

(In reply to David Cook from comment #1)
> tuxayo:
> > For us: is there still data in RabbitMQ when stopping a Koha instance and
> > upgrading it? [...]
> 
> [...]
> 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.

Is it something that regularly happens? (have messages in RabbitMQ that haven't
been processed) With the reasonable assumption that people don't upgrade Koha
in the middle of a day with librarians doing things that use the queue/workers.

Or is it something that totally happens?
Maybe the assumption is wrong or there is another source of messages that is
unavoidable.

-- 
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/

Reply via email to