https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35920 --- Comment #31 from Tomás Cohen Arazi (tcohen) <tomascohen@gmail.com> --- (In reply to David Cook from comment #29)
(In reply to Tomás Cohen Arazi (tcohen) from comment #28)
This was my original idea, pretty much what David suggests.
Sorry for missing that before!
I was trying to write it this morning when I hit a roadblock: I wanted to prepare it to support delayed retries, and figured it would require manually installing and maintaining the setup for the delayed queue plugin (not shipped in Debian).
And I understood this would need to be set to not-default for the general public because of that. So a niche use case with too little gain so far. So the question is: who’s gonna maintain that? Implementing a feature would require doing it in both for sure. Who would do it?
Those are my questions.
Yeah, I just saw that bug report. I've added some comments there. I think that the solution for delayed retries should be found in a task scheduler rather than a job worker. That's even the solution suggested by the developer of that RabbitMQ plugin.
That's actually something I bumped into with bug 10662 because I was performing OAI-PMH harvests using background job workers, and I needed to be able to schedule future harvests. I did that by having the worker add a task to the task scheduler.
Compare adding a column `run_after` of type timestamp with adding yet another subsystem to maintain. We need to match timezones, I need to sleep now, this is a great chat -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.