https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41223
Michaela Sieber <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|25.05 |Main Status|ASSIGNED |CONFIRMED --- Comment #8 from Michaela Sieber <[email protected]> --- The situation will improve somewhat with the planned ERM usage improvements, as we will then be able to identify more easily in the provider summary that a retry is required when COUNTER Error 1020 is returned. In addition, this could be handled automatically through retry management. Another approach could be to insert the background jobs created by the erm_run_harvester cron job into the database with a delay of 1–2 seconds between each job. Description Koha::ERM::EUsage::UsageDataProvider::enqueue_sushi_harvest_jobs enqueues the erm_sushi_harvester background jobs one right after the other, without any delay. As a result, the jobs for a provider [get identical or near-identical enqueued_on timestamps / hit the SUSHI service at the same moment . Proposed solution Add a one-second pause between consecutive enqueue calls in enqueue_sushi_harvest_jobs (no pause before the first or after the last job). Return value and parameters stay unchanged. A unit test should check the time difference between the enqueued_on values. Note The delay only affects enqueuing. If jobs should also be processed sequentially, that needs a different approach (e.g. a single worker or a dedicated queue). -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected] website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
