Val, Yes, with same affinity function entries with same key should be saved in same nodes. As far as I know, primary node is assinged automatically by Ignite. And I'm not sure that there is a guarantee that 2 entries from different caches with same key will have same primary and backup nodes. So, get operation for 1-st key can be local while get() for 2-nd key will be remote.
On Thu, Feb 23, 2017 at 6:49 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > 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.mashen...@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 <al...@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 > > > -- Best regards, Andrey V. Mashenkov
