#856: BibSched: tasks not halting the queue on failure
------------------------+-------------------------
Reporter:  jlavik       |       Owner:
    Type:  enhancement  |      Status:  infoneeded
Priority:  critical     |   Component:  BibSched
 Version:               |  Resolution:
Keywords:               |
------------------------+-------------------------
Changes (by skaplun):

 * status:  assigned => infoneeded


Comment:

 At [http://invenio-software.org/repo/personal/invenio-sam/log/?h=bibsched-
 nostop sam/bibsched-nostop] there is a squashed version of this branch on
 top of master.

 To me, the failure of task as whole could fall in either CERROR Vs. ERROR
 status depending on two things:
 1. if the task is introducing changes that cannot be replied from the
 current status of the system (i.e. BibUpload). From this point of view,
 bibreformat, webcoll, bibindex, bibclassify, refextract,
 oai_repository_update etc. can all recover from the current state of the
 system (e.g. at worse bibindex can be re-indexed).
 2. if the admin decided that a given bibtask is a requirement for the QoS
 of his repository (say oaiharvest should never fails!)

 For that reason I would propose that:
 1. by default only ''bibupload'' finishes with an '''ERROR''', and every
 other task with a '''CERROR'''.
 2. a new CLI argument is introduced to bibtask in order to let the admin
 to specify if a given task is critical or not. (e.g. '''--stop-queue-on-
 error'''). Such flag should also be understood by
 task_low_level_submission.

-- 
Ticket URL: <http://invenio-software.org/ticket/856#comment:12>
Invenio <http://invenio-software.org>

Reply via email to