Bug 6138 - Interrupt staging if jobs are terminated and staging is active
: Interrupt staging if jobs are terminated and staging is active
Status: RESOLVED FIXED
: GRAM
wsrf managed execution job service
: alpha
: Macintosh All
: P3 major
: 4.2
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2008-06-09 11:57 by
Modified: 2008-06-09 12:16 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2008-06-09 11:57:19
While Gram4 tries to cancel a job at the local resource manager, if the job
is currently running in the local resource manager when a client calls
destroy() for the job, it never interrupted a currently running staging if
a job was in the middle of staging when the client calls destroy() for the
job.
In fact it doesn't even wait for the staging to be completed before starting
the clean up steps.

Solution:

In 4.2 Gram interrupts stageIn and stageOut by destroying the transfer
resources before the cleanup steps are started. fileCleanUp is not
interrupted, because this would have to be performed anyway in termination.