Bugzilla – Bug 5833
Setting termination time on MultiJob resources
Last modified: 2008-04-04 08:07:17
You need to
before you can comment on or make changes to this bug.
Currently only the termination time of the MultiJob resource is updated,
sub-jobs are not updated.
It makes sense though to forward the new termination time to all sub-jobs
and all corresponding subscription resources. A failure in updating the
termination time of a sub-job does not prevent from attempts to update the
termination-time of all other sub-jobs, but the termination-time of the
MultiJob resource will not be updated and an exception is thrown to inform
the client about the problem.
When a client updates the terminationTime of a MultiJobResource:
in case an error happens on updating the termination time on a SubJob (SJ) a
TerminationTimeRejectedException is thrown and the termination time of the
MultiJobResource is set back to the original value. But there's no attempt
to set the termination time of those SubJobs for which the update succeeded
back to the original value.
Is this policy ok: "if there's an exception when updating the termination
time of a multi job we don't guarantee for the termination time of the
I think it is, because there might be errors when setting the terminationTime
of a SJ back to the original value. So we probably can't give hard guarantees.
And finally a client has the possibility to update the termination time of
the SJ's manually.