[
https://issues.apache.org/jira/browse/IGNITE-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov updated IGNITE-2310:
---------------------------------
Description:
For jobs executed using affinityRun/affinityCall methods need to make sure that
node executing job owns required cache partition and partition is not moved
while job runs.
Also need to add methods with list of caches: affinityRun(Collection<String>
cacheNames, Object affKey, IgniteRunnable job), affinityCall(Collection<String>
cacheNames, Object affKey, IgniteCallable<R> job), for this methods need to
make sure that parition in all caches is available while job runs.
Note: similar logic waiting/blocking partitions in already implemented for sql
queries.
was:Need to add public API methods that will allow to lock and unlock
partitions. This may be useful to avoid data movements when using
{{affinityRun}} during topology changes.
> Lock cache partition for affinityRun/affinityCall execution
> -----------------------------------------------------------
>
> Key: IGNITE-2310
> URL: https://issues.apache.org/jira/browse/IGNITE-2310
> Project: Ignite
> Issue Type: New Feature
> Components: cache
> Reporter: Valentin Kulichenko
> Assignee: Semen Boikov
> Priority: Critical
> Labels: community
> Fix For: 1.6
>
>
> For jobs executed using affinityRun/affinityCall methods need to make sure
> that node executing job owns required cache partition and partition is not
> moved while job runs.
> Also need to add methods with list of caches: affinityRun(Collection<String>
> cacheNames, Object affKey, IgniteRunnable job),
> affinityCall(Collection<String> cacheNames, Object affKey, IgniteCallable<R>
> job), for this methods need to make sure that parition in all caches is
> available while job runs.
> Note: similar logic waiting/blocking partitions in already implemented for
> sql queries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
