Bugzilla – Bug 5836
Change in persistence behavior of Gram4 job resources
Last modified: 2008-02-06 14:17:15
You need to
before you can comment on or make changes to this bug.
So far a job resource is persisted to disk if an element of the state of
the resource changes. This is about 17 times in a simple job without
staging. I changed this so that a resource is only persisted at the end
of each processing step of an internal state. This reduces the number of
persistence actions to about 10 times in a simple job without staging.
With the new shutdown behavior in Gram in 4.2 it is ensured that a processing
step will not be interrupted in the middle of processing in an orderly JVM
If the JVM is killed a resource will resume processing in the last internal
state that had been persisted to disk.
By this we avoid the potential to have inconsistent persisted resource state
where some but not all elements had already been updated to the new state.