public interface CollisionContext
ComputeJobContinuation
), then collection of held jobs will
always be empty. CollisionSpi
will manipulate these lists
to make sure that only allowed number of jobs are running in parallel or
waiting to be executed.Modifier and Type | Method and Description |
---|---|
Collection<CollisionJobContext> |
activeJobs()
Gets ordered collection of collision contexts for jobs that are currently executing.
|
Collection<CollisionJobContext> |
heldJobs()
Gets collection of jobs that are currently in
held state. |
Collection<CollisionJobContext> |
waitingJobs()
Gets ordered collection of collision contexts for jobs that are currently waiting
for execution.
|
Collection<CollisionJobContext> activeJobs()
null
.Collection<CollisionJobContext> waitingJobs()
null
. Note that a newly
arrived job, if any, will always be represented by the last item in this list.
This list is guaranteed not to change while
CollisionSpi.onCollision(CollisionContext)
method is being executed.
Collection<CollisionJobContext> heldJobs()
held
state. Job can enter
held
state by calling ComputeJobContinuation.holdcc()
method at
which point job will release all resources and will get suspended. If
job continuations
are not used, then this list
will always be empty, but never null
.held
state.
Follow @ApacheIgnite
Ignite Database and Caching Platform : ver. 2.16.0 Release Date : December 15 2023