ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yakov Zhdanov <yzhda...@apache.org>
Subject Re: ignite-2310
Date Wed, 06 Jul 2016 12:14:32 GMT
Guys, this does not work in general case. If you provide more than one
partition you can end up with a situation when they reside on more than one
node.

--Yakov

2016-07-06 13:50 GMT+03:00 Vladimir Ozerov <vozerov@gridgain.com>:

> If we add "partsToLock" to job execute request, then why we allow it only
> for "affinity" methods? We can resort to "with" semantics instead:
>
> IgniteCompute.*withPartitionsToLock*(...).affinityRun();
>
> On Wed, Jul 6, 2016 at 12:23 PM, Taras Ledkov <tledkov@gridgain.com>
> wrote:
>
> > Igniters,
> >
> > Lets discuss the changes of public API at the IgniteCompute.
> > The new methods affinityRun & affinityCall is added by working on
> > IGNITE-2310.
> >
> > https://issues.apache.org/jira/browse/IGNITE-2310
> >
> > Please take a look at the signature of the new methods:
> >
> >
> >
> https://github.com/gridgain/apache-ignite/commit/991fb60f563ee1630152ca0159d04b4969f883bf#diff-b276b8e6e14915f9e5f2f5daeeddec8a
> >
> > void affinityRun(@Nullable String cacheName, Object affKey,
> IgniteRunnable
> > job, Map<String, int[]> partsToLock)
> >
> > The parameter Map<String, int[]> partsToLock is added.
> > Map contains the pairs of the cache name and array of partitions that
> must
> > be reserved on the target node before job execution.
> >
> > Dmitry, colleagues, please comment or approve.
> >
> > --
> > Taras Ledkov
> > Mail-To: tledkov@gridgain.com
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message