Comment 1 for bug 1185865

Evergreen Indiana Consortium is on 2.2 so this may or may not relate. Our utility server handles the holds targeter and recently it crashed in off hours. We restarted processes during core library hours and noticed that due to the manner in which the select is performed (holds not checked in last 24 hours or later) the holds targeting was being performed during library core hours. The processing appears to be spreading out over time as Ben describes in his original bug report due to the 15 minute cron running of the job and the length of time it actually takes to process the 12K of holds that we have. However, the spread is currently only through library core hours and none have actually been moved outside of those hours for processing.