[saga-rg] job states...

[Andre Merzky]

Hi group, 

It seems I am lacking some understanding of the SAGA job
states, and would appreciate if someone with more knowledge
about job management could answer some questions (Chris, are
you still watching this list by any chance?)

Attached to this mail is a draft of a SAGA job state
diagram.  For simplicity, I did not distinguish between
UserHold and SystemHold, nor between UserSuspend and
SystemSuspend.  The arrows show possible state changes, the
method names denote methods which can initiate state changes
from API level.

I think that diagram is wrong, isn't it?  Well, here are my
questions:

  - if we submit a job, its immediately Queued - is that
    right?  Should it be pending before (e.g. as long as the
    queuing request travels the middleware layers)?

  - can the hold and suspend states reached only from
    'Running', or from elsewhere as well?

  - What is the difference between 'Hold' and 'Suspend'?

  - Are there signals defined (apart from KILL) which shange
    the job state?  I guess that is not as simple as saying
    SUSP does suspend - that state is probably defined by
    the scheduler, not by the OS...

  - What is the use case for distinguishing between UserHold
    and SystemHold, or between UserSuspend and
    SystemSuspend?
    

I would like to understand these states, in particular in
correspndence to the task states we have.  Well, I put
questions to that relation in another mail - to keep this
mail 'short'.

Thanks, Andre.


-- 
"So much time, so little to do..."  -- Garfield
-------------- next part --------------
A non-text attachment was scrubbed...
Name: job_states.png
Type: image/png
Size: 23305 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/saga-rg/attachments/20060204/ace99294/attachment-0003.png