https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30654
--- Comment #13 from Tomás Cohen Arazi <tomasco...@gmail.com> --- Send message to a durable RabbitMQ queue(In reply to David Cook from comment #10) > 4. Send message to a durable RabbitMQ queue What is the 'durable RabbitMQ queue' in this context? In order for using RabbitMQ makes sense, I feel like we need: - A Task queue manager (we have the table, just missing a process that polls it and sends 'the message' - A way to dispatch the message to notify workers about it (Yay, RabbitMQ) - A worker that reads the message and acts accordingly Questions: - how does a worker report back if it failed? Probably directly to the DB? This is a case for a task queue manager, which would read and make the decision it is time to retry. - if we had 2 workers waiting for 'index' jobs through the mq, how do we pick which process takes the job? how does the system know it is being processed by who? what if the process dies and we need to assign a new worker? That's where I was going with the PID thing. BEcause I was thinking about things locally (wrong) but the case still stands with this question. Who is running what? I personally don't see a case in which RabbitMQ is being useful right now. At least when we still haven't implemented a way to avoid tasks that failed to get notified through the mq to be retried, scheduled, etc. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org 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/
