After a week of running this in production, we have had an improvement in events processing. We no longer run out of open-ils.trigger drones and we no longer have the "Event reacting failed with Can't call method "request" on an undefined value at /usr/local/share/perl/5.30.0/OpenILS/Application/Trigger/Reactor/Circ/AutoRenew.pm line 88" error message.
The number of stuck and error'd auto-renewal events appears to have dropped.
We do still have issues processing some events in the wee hours of the morning, but I think those are other bugs and may be alleviated by adjusting our cron schedules.
I have therefore pushed the branch to main, rel_3_11, and rel_3_10, with a short release note to indicate a potential issue is resolved.
Thanks to Galen for signing off, and thanks to Bill for the original code for the fix that needed small modification to work in stock Evergreen.
After a week of running this in production, we have had an improvement in events processing. We no longer run out of open-ils.trigger drones and we no longer have the "Event reacting failed with Can't call method "request" on an undefined value at /usr/local/ share/perl/ 5.30.0/ OpenILS/ Application/ Trigger/ Reactor/ Circ/AutoRenew. pm line 88" error message.
The number of stuck and error'd auto-renewal events appears to have dropped.
We do still have issues processing some events in the wee hours of the morning, but I think those are other bugs and may be alleviated by adjusting our cron schedules.
I have therefore pushed the branch to main, rel_3_11, and rel_3_10, with a short release note to indicate a potential issue is resolved.
Thanks to Galen for signing off, and thanks to Bill for the original code for the fix that needed small modification to work in stock Evergreen.