Suspending a session
About this task
When a session is suspended, any running tasks are given a grace period
(suspendGracePeriod in the application profile) to finish. If they do not
finish before the grace period, the service instances, on which they are running, are terminated and
the tasks are re-queued and put into the pending state. No pending tasks are scheduled until the
session is resumed. Any tasks that were re-queued are rerun when the session resumes.
Note: In the
case where you suspend a task after the host has been reclaimed, the grace period defined in
suspendGracePeriod will be ignored, and the
reclaimGracePeriod will be used instead. ![([7.3.2 Fix]](../732fix.gif)
However,
if the task finish time from suspendGracePeriod is earlier than the reclaiming
time (reclaimGracePeriod), set
SOAM_SSM_UPDATE_RELEASE_TIMEOUT=true in the SOAM section of the application
profile so that the IBM® Spectrum Symphony uses (not ignores) the suspendGracePeriod value. For example, for a session
where reclaimGracePeriod is 3600 seconds, and
suspendGracePeriod is 30 seconds, if the host is reclaimed and then the session
is suspended, a slot with a long running task can be released after 30 seconds (the
suspendGracePeriod value) instead of 3600 seconds.
However,
if the task finish time from suspendGracePeriod is earlier than the reclaiming
time (reclaimGracePeriod), set
SOAM_SSM_UPDATE_RELEASE_TIMEOUT=true in the SOAM section of the application
profile so that the IBM® Spectrum Symphony uses (not ignores) the suspendGracePeriod value. For example, for a session
where reclaimGracePeriod is 3600 seconds, and
suspendGracePeriod is 30 seconds, if the host is reclaimed and then the session
is suspended, a slot with a long running task can be released after 30 seconds (the
suspendGracePeriod value) instead of 3600 seconds.