This is an automated notification sent by LCG Savannah.
It relates to:
task #7321, project CDS Invenio
==============================================================================
LATEST MODIFICATIONS of task #7321:
==============================================================================
Follow-up Comment #1, task #7321 (project cdsware):
This option would be dangerous without a notion of task dependencies. Imagine
two jobs, bibupload1 and bibupload2, with bibupload2 depending on bibupload1.
If 1 fails, and 2 would go, then bad things would happen. It is much safer to
stop the queue if a bibupload fails, as it usually necessitates human's
intervention to resolve the problem.
On the other hand, if a bibindex/bibrank/etc job fails, then we may still be
accepting further bibuploads without too much risk.
Hence it is better to think here not in terms stopping the queue, but in
terms of allowing/forbidding certain tasks after a failure. E.g. if a
bibupload task fails, no further bibupload tasks should be permitted until
the first failed task is solved and acknowledged. E.g. if a bibindex task
fails, no further bibindex task should be permitted, but other jobs such as
bibuploads are okay. Etc.
(... and I don't think that working hours or not should make a difference
here.)
==============================================================================
OVERVIEW of task #7321:
==============================================================================
URL:
<http://savannah.cern.ch/task/?7321>
Summary: bibsched scheduler should not block inside given
hours
Project: CDS Invenio
Submitted by: skaplun
Submitted on: 2008-07-05 09:22
Should Start On: 2008-07-05 00:00
Should be Finished on: 2008-07-05 00:00
Category: BibSched
Priority: 5 - Normal
Status: None
Privacy: Private
Percent Complete: 0%
Assigned to: skaplun
Open/Closed: Open
Discussion Lock: Any
Effort: 0.00
_______________________________________________________
bibsched scheduler blocks on purpose warning the admin, when a task terminate
with an error.
This is not desirable outside administrator working hours (e.g. weekends)
because blocking the whole queue is worse than not recovering correctly the
error (usually).
A way to instruct bibsched which hours should keep going must be added.
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
List-Post: project-invenio-devel@cern.ch
Date: 2008-07-07 08:05 By: Tibor Simko <simko>
This option would be dangerous without a notion of task dependencies. Imagine
two jobs, bibupload1 and bibupload2, with bibupload2 depending on bibupload1.
If 1 fails, and 2 would go, then bad things would happen. It is much safer to
stop the queue if a bibupload fails, as it usually necessitates human's
intervention to resolve the problem.
On the other hand, if a bibindex/bibrank/etc job fails, then we may still be
accepting further bibuploads without too much risk.
Hence it is better to think here not in terms stopping the queue, but in
terms of allowing/forbidding certain tasks after a failure. E.g. if a
bibupload task fails, no further bibupload tasks should be permitted until
the first failed task is solved and acknowledged. E.g. if a bibindex task
fails, no further bibindex task should be permitted, but other jobs such as
bibuploads are okay. Etc.
(... and I don't think that working hours or not should make a difference
here.)
_______________________________________________________
Carbon-Copy List:
CC Address | Comment
------------------------------------+-----------------------------
1576 | -COM-
2195 | -SUB-
==============================================================================
This item URL is:
<http://savannah.cern.ch/task/?7321>
_______________________________________________
Message sent via/by LCG Savannah
http://savannah.cern.ch/
