You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
should we add a lock file (or similar, e.g. flag in the DB) indicating that C2M check_existence is already running, so that the cron jobs don't step on one another and pick up the same list of least-recently-checked objects if they run long?
The text was updated successfully, but these errors were encountered:
ndushay
changed the title
(C2M) run check_existence continuously against the least recently checked catalog entries
(C2M) run C2M continuously against the least recently checked catalog entries
Jan 25, 2018
ndushay
changed the title
(C2M) run C2M continuously against the least recently checked catalog entries
(C2M) run C2M "continuously" against the least recently checked catalog entries
May 15, 2018
current plan, in #648, is to run every other week via cron (whenever).
after that, we may do any of the following:
run all the roots in parallell, effectively starting a job that runs the rake task for a single storage root ... for each of the storage roots. (one process per root)
determine the longest time needed for any storage root, and possibly run cron every XXX depending on that interval.
switch to using redis to kick off C2M for individual druids
questions:
check_existence
is already running, so that the cron jobs don't step on one another and pick up the same list of least-recently-checked objects if they run long?The text was updated successfully, but these errors were encountered: