https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32573
--- Comment #18 from David Cook <[email protected]> --- (In reply to Tomás Cohen Arazi from comment #17) > Regarding the ack discussion, it feels to me that many of our problems are > related to the 'ack last' behavior. As you said, we have our own way of > tracking progress and termination, so we are safe to just ack and leave that > to Koha. Well, I think the end user can track the progress, but we don't currently have a systematic way of catching "stuck" jobs. But that's a failure scenario that should hopefully be rarer than consumer acknowledgement timeouts. We'll get there. I'm curious to hear what Michael and Luke from RabbitMQ advise... > I've been pondering having separate workers for polling and rabbit > respectively. It would simplify things a lot. That does sound interesting. Could you explain that one more? -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ 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/
