#991: Allow tasks to execute on the host set in "host" field
--------------------+-----------------------
Reporter: adeiana | Owner:
Type: defect | Status: assigned
Priority: major | Component: BibSched
Version: | Resolution:
Keywords: |
--------------------+-----------------------
Comment (by adeiana):
Let's take this further,
I see multiple reasons not dependent of our code that would make it long
to start.
Particularly an unresponsive AFS leaving the processes in D state for
several seconds.
or there is a problem on startup we never reach the startup and enter some
deadlock.
We have the same exact problem with RUNNING tasks.
If they were kill by the oom killer, they remain in RUNNING status. I
already had this happening too.
Depending on our need to differentiate a starting task from a running
task.
If needed, we can add a STARTING status, if not we mark the task as
RUNNING.
All tasks in starting status can behave like running as a result will have
the queue entering the current deadlock we have.
In a separate ticket we handle pinging tasks regularly to check that they
are not dead.
Viable solution?
--
Ticket URL: <http://invenio-software.org/ticket/991#comment:11>
Invenio <http://invenio-software.org>
