You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Taras Ledkov <tl...@gridgain.com> on 2017/02/17 10:50:41 UTC
Re: Locking of partition with affinityRun/affinityCall
Denis,
Please review the javadoc of the affinity jobs.
PR: https://github.com/apache/ignite/pull/1550
On 08.12.2016 12:06, Taras Ledkov wrote:
> Denis,
>
> The second point is absolutely correct.
> The rebalancing isn't blocked. The partition will not be evicted while
> the partition is reserved.
>
> I'll update javadoc ASAP.
>
>
> On Wed, Nov 30, 2016 at 10:23 PM, Denis Magda <dmagda@apache.org
> <ma...@apache.org>> wrote:
>
> Taras,
>
> There is a question in regards to the feature contributed by you
> recently
> https://issues.apache.org/jira/browse/IGNITE-2310
> <https://issues.apache.org/jira/browse/IGNITE-2310>
>
> The Java API doc says that the partition will not be migrated
> while a job is being executed on a target node.
>
> Does it mean that
> - the rebalancing will be postponed in general or
> - the rebalancing of the partition will be started, moving its
> content to a new primary, but the partition will not be evicted
> from the target node while the job is running
>
> In my understanding the second point is correct and I\u2019ve
> documented the feature saying that the partition is not evicted
> http://apacheignite.gridgain.org/v1.7/docs/collocate-compute-and-data#affinity-call-and-run-methods
> <http://apacheignite.gridgain.org/v1.7/docs/collocate-compute-and-data#affinity-call-and-run-methods>
>
> Please clarify what\u2019s true and update Java API doc if my current
> understanding is correct.
>
> \u2014
> Denis
>
>
--
Taras Ledkov
Mail-To: tledkov@gridgain.com