Incorrect copy status caused by reshelving process colliding with item checkout
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.1 |
Fix Released
|
Medium
|
Unassigned | ||
3.2 |
Fix Released
|
Medium
|
Unassigned | ||
3.3 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Evergreen 2.1+
In a busy production system with a large database, the reshelving-complete script can take several minutes to run. This can lead to the following scenario:
copy checked in -> status 7
copy picked up for processing by the reshelving-complete process
copy checked out -> status 1
reshelving-complete process completes -> status 0.
This results in an open circulation on a copy with a status of 0, which apart from just being wrong, prevents renewals of the circulation due to bad copy status.
The occurrence increases the more often the reshelving-complete process is run. For example, running it hourly in a busy system creates many (relatively speaking) opportunities for this to happen.
Changed in evergreen: | |
milestone: | 2.2.1 → 2.2.2 |
no longer affects: | evergreen/2.1 |
no longer affects: | evergreen/master |
Changed in evergreen: | |
milestone: | 2.4.0-beta → 2.4.0-rc |
Changed in evergreen: | |
milestone: | 2.4.0-rc → none |
no longer affects: | evergreen/2.2 |
no longer affects: | evergreen/2.4 |
no longer affects: | evergreen/2.3 |
no longer affects: | evergreen/2.5 |
no longer affects: | evergreen/2.6 |
no longer affects: | evergreen/2.7 |
tags: | added: pullrequest |
tags: | added: checkout |
Confirmed to occur in our 2.2 systems. Just had a case reported today, but there may be others lurking.