ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Valentin Kulichenko <valentin.kuliche...@gmail.com>
Subject Re: Same Affinity For Same Key On All Caches
Date Thu, 23 Feb 2017 15:49:36 GMT
Actually, this should work this way out of the box, as long as the same
affinity function is configured for all caches (that's true for default
settings).

Andrey, am I missing something?

-Val

On Thu, Feb 23, 2017 at 7:02 AM, Andrey Mashenkov <
andrey.mashenkov@gmail.com> wrote:

> Hi Alper,
>
> You can implement you own affinityFunction to achieve this.
> In AF you should implement 2 mappings: key to partition and partition to
> node.
>
> First mapping looks trivial, but second doesn't.
> Even if you will lucky to do it, there is no way to choose what node wil be
> primary and what will be backup for a partition,
> that can be an issue.
>
>
> On Thu, Feb 23, 2017 at 10:44 AM, Alper Tekinalp <alper@evam.com> wrote:
>
> > Hi all.
> >
> > Is it possible to configures affinities in a way that partition for same
> > key will be on same node? So calling
> > ignite.affinity(CACHE).mapKeyToNode(KEY).id() with same key for any
> cache
> > will return same node id. Is that possible with a configuration etc.?
> >
> > --
> > Alper Tekinalp
> >
> > Software Developer
> > Evam Streaming Analytics
> >
> > Atatürk Mah. Turgut Özal Bulv.
> > Gardenya 5 Plaza K:6 Ataşehir
> > 34758 İSTANBUL
> >
> > Tel:  +90 216 455 01 53 Fax: +90 216 455 01 54
> > www.evam.com.tr
> > <http://www.evam.com>
> >
>
>
>
> --
> Best regards,
> Andrey V. Mashenkov
>

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