Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.apache.org
Date: Mon, 17 Jul 2017 10:26:53 -0700 (MST)
From: vkulichenko <valentin.kulichenko@gmail.com>
To: user@ignite.apache.org
Message-ID: <1500312413003-15015.post@n6.nabble.com>
In-Reply-To: <CAJYNqUJhVdNYb8A_m4QQ9rEdi6DZXEoEPJqPimKnhpLpuu-E7A@mail.gmail.com>
References: <CAJYNqUJhVdNYb8A_m4QQ9rEdi6DZXEoEPJqPimKnhpLpuu-E7A@mail.gmail.com>
Subject: Re: Compute Grid Questions
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
archived-at: Mon, 17 Jul 2017 17:27:04 -0000

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.