[Koha-bugs] [Bug 35165] New: Batch item deletions are run in a single transaction and cause locking issues

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35165

            Bug ID: 35165
           Summary: Batch item deletions are run in a single transaction
                    and cause locking issues
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: major
          Priority: P5 - low
         Component: Tools
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: nick at bywatersolutions.com
        QA Contact: testopia at bugs.koha-community.org

We recently saw a site perform a batch deletion of ~18k items (and subsequently
2k bibs)

While running the jobs we suddenly started seeing all sorts of actions fail,
most notably placing reserves, and errors in the logs like:
DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st
execute failed: Lock wait timeout exceeded; try restarting transaction at
/usr/share/koha/lib/Koha/Object.pm line 170

I believe part of the problem is that the entire batch deletion is a single
transaction.

While we should make parts of this atomic, I don't think the entire job should
succeed or fail on an error. I think we should commit each item, then each bib,
then continue.

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.