Hi Matt, 1. Each task or closure execution creates a session that has an ID. You can cast returned IgniteFuture to ComputeTaskFuture (unfortunately there is no other way now) and then use getTaskSession() method to get the session description. However, this information is available only on the node that executed the job, there is currently no way to cancel it from other client.
2. When job is cancelled, thread that is running it is interrupted. Job should check the interrupted flag and stop the execution if needed. 3. See #1. Having session ID, you can get a future for a task and then cancel it. But again, it's all local - this state is not shared across nodes. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Compute-Grid-Questions-tp14980p15015.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
