Re: Same Affinity For Same Key On All Caches

2017-03-02 Thread Denis Magda
vous > function? > > In my view issue discussed here makes it pretty much useless in vast > majority of use cases, and very error-prone in all others. > > -Val > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Same

Re: Same Affinity For Same Key On All Caches

2017-03-02 Thread Valentin Kulichenko
se outline its advantages vs rendezvous > function? > > In my view issue discussed here makes it pretty much useless in vast > majority of use cases, and very error-prone in all others. > > -Val > > > > -- > View this message in context: http://apache-ignite-users. >

Re: Same Affinity For Same Key On All Caches

2017-03-01 Thread Andrey Mashenkov
8] => [127.0.0.1, > 192.168.1.42][127.0.0.1, 192.168.1.42] => [127.0.0.1, > 192.168.1.28][127.0.0.1, 192.168.1.28] => [127.0.0.1, 192.168.1.42]* > > That is what I found while debugging. Sorry for verbose mail. > > > On Tue, Feb 28, 2017 at 9:56 AM, Alper Tekinalp wrote:

Re: Same Affinity For Same Key On All Caches

2017-02-27 Thread Alper Tekinalp
Hi. As I investigated the issue occurs when different nodes creates the caches. Say I have 2 nodes node1 and node2 and 2 caches cache1 and cache2. If I create cache1 on node1 and create cache2 on node2 with same FairAffinityFunction with same partition size, keys can map different nodes on differ

Re: Same Affinity For Same Key On All Caches

2017-02-23 Thread Alper Tekinalp
Hi. Thanks for your comments. Let me investigate the issue deeper. Regards. On Thu, Feb 23, 2017 at 11:00 PM, Dmitriy Setrakyan wrote: > If you use the same (or default) configuration for the affinity, then the > same key in different caches will always end up on the same node. This is > guara

Re: Same Affinity For Same Key On All Caches

2017-02-23 Thread Dmitriy Setrakyan
If you use the same (or default) configuration for the affinity, then the same key in different caches will always end up on the same node. This is guaranteed. D. On Thu, Feb 23, 2017 at 8:09 AM, Andrey Mashenkov < andrey.mashen...@gmail.com> wrote: > Val, > > Yes, with same affinity function en

Re: Same Affinity For Same Key On All Caches

2017-02-23 Thread Andrey Mashenkov
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,

Re: Same Affinity For Same Key On All Caches

2017-02-23 Thread Valentin Kulichenko
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, > >

Re: Same Affinity For Same Key On All Caches

2017-02-23 Thread Andrey Mashenkov
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 b

Same Affinity For Same Key On All Caches

2017-02-22 Thread Alper Tekinalp
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 Develo