#158: BibSched erroneously thinks that tasks failed to run
-----------------------+----------------------
Reporter: skaplun | Owner: skaplun
Type: defect | Status: assigned
Priority: critical | Milestone:
Component: BibSched | Version:
Resolution: | Keywords:
-----------------------+----------------------
Comment (by skaplun):
Case study 1 is very interesting indeed.
Something to know, indeed, is that that it's responsibility of the task to
update its status in the DB (and the task is doing this at the very end of
its main execution). This is the information bibsched is actually waiting
for in order to organize the scheduling of task. On the other and the line
in the log, is written via a hack, using a shell script that is called
exactly after the task ends (so actually after it has cleared all the
memory, garbage collected etc.) The fact that bibindex starts 10 seconds
before bibrank ends (according to the logs) can be read as bibrank
actually taking ~10 seconds in order to close after it has finishes...
This is a possible symptom of lots of memory being used by complex
structures, i.e. citation dictionary :-)
--
Ticket URL: <https://invenio-software.org/ticket/158#comment:4>
Invenio <http://invenio-software.org>
