This is an automated notification sent by LCG Savannah.
It relates to:
task #6786, project CDS Invenio
==============================================================================
LATEST MODIFICATIONS of task #6786:
==============================================================================
Update of task #6786 (project cdsware):
Status: None => Done
Percent Complete: 20% => 100%
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #2:
New --runtime-range CLI param has been implemented. If task is run outside
the range it is postponed to the next good range.
==============================================================================
OVERVIEW of task #6786:
==============================================================================
URL:
<http://savannah.cern.ch/task/?6786>
Summary: introduce task runtime limit
Project: CDS Invenio
Submitted by: simko
Submitted on: 2008-04-24 09:56
Should Start On: 2008-04-24 00:00
Should be Finished on: 2008-04-24 00:00
Category: BibSched
Priority: 5 - Normal
Status: Done
Privacy: Public
Percent Complete: 100%
Assigned to: skaplun
Open/Closed: Closed
Discussion Lock: Any
Effort: 0.00
_______________________________________________________
For certain maintenance tasks, a new concept of a "runtime limit"
would be advantageous. Use case 1: run inveniogc every night when the
task queue is empty, but start the task only from 23:00 until 02:00,
not later. Use case 2: run bibrank word similarity rebalancing every
Sunday from 21:00 until 05:00, but do not start the task outside this
day or outside this hour interval; and if the bibsched is busy with
other tasks, then run it next Sunday only.
This should be implemented via a new task "runtime limit" option. We
don't need to go too fancy like cron, a day of the week and an hour
interval should be enough. BibSched should then look for WAITING
tasks as before, and consult the task runtime limit, and either run
the task if the limit is met, or reschedule it for the next possible
day and hour depending on the runtime limits.
(Alternatively, and more laboriously, these tasks could get scheduled
and get run via a different scheduling mechanism, e.g. the task status
would be "DAEMON" with a descriptive daemontime "Sunday 23:00-05:00".
These daemon tasks would retain the same task ID forever,
e.g. inveniogc would get taskID 1, and would be awaken by bibsched
when the queue is empty and the daemontime limit is met, and would
write to the same bibsched_task_1.{log,err} files every time awaken.
We could extend this DAEMON-like concept to bibindex etc daemons, with
descriptive daemontime like "Every 5 min", etc.)
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: 2008-10-31 14:30 By: Samuele Kaplun <skaplun>
New --runtime-range CLI param has been implemented. If task is run outside
the range it is postponed to the next good range.
-------------------------------------------------------
Date: 2008-05-15 16:15 By: Samuele Kaplun <skaplun>
The deamon behaviour of this Task is somehow now implemented. No DAEMON
special status, just if the bibtask comes with a sleeptime set then it will
behave as a daemon.
_______________________________________________________
Carbon-Copy List:
CC Address | Comment
------------------------------------+-----------------------------
2195 | -COM-
1576 | -SUB-
==============================================================================
This item URL is:
<http://savannah.cern.ch/task/?6786>
_______________________________________________
Message sent via/by LCG Savannah
http://savannah.cern.ch/
