https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36484
--- Comment #7 from Alex Buckley <[email protected]> --- (In reply to David Cook from comment #5) > This change doesn't make sense to me. > > What's the scenario where you'd need this? Hi David, The use case we have is, a partner library has 359 background jobs with: - type='update_elastic_index' - status='new' Even though koha-worker and koha-es-indexer are running these 359 jobs are stuck on the status of new and are not being processed. RabbitMQ is not looking for outstanding jobs instead it is only listening to new jobs - in a similar situation to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30654 This enhancement ensures when we start koha-common services like koha-worker and koha-es-indexer all these new 'update_elastic_index' jobs are processed and not ignored. -- 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/
