https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32573 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |In Discussion --- Comment #14 from David Cook <dcook@prosentient.com.au> --- Regarding the subject of early ACK and late ACK, consider the following RabbitMQ discussion between a user and 2 key RabbitMQ devs (both I've spoken to personally in the past): https://github.com/rabbitmq/rabbitmq-server/discussions/4030 Luke's recommendation is to update the global consumer timeout. Michael mentions most consumers shouldn't need longer than 30 minutes to process a message, but for operations that are expected to take longer than 30 minutes - you can ACK early and use a separate progress metric. Since we're using the database result store, end users can use that as a progress metric. And if we have a cronjob that runs periodically, we can evaluate the start time and fail tasks that run longer than our own configurable timeout. I think that would resolve this ACK issue perfectly. -- You are receiving this mail because: You are watching all bug changes.