Re: Same Affinity For Same Key On All Caches

[Denis Magda]

What??? Unbelievable. It sounds like a design flaw to me. Any ideas how to fix?

—
Denis

> On Mar 2, 2017, at 2:43 PM, Valentin Kulichenko 
> <valentin.kuliche...@gmail.com> wrote:
> 
> Adding back the dev list.
> 
> Folks,
> 
> Are there any opinions on the problem discussed here? Do we really need 
> FairAffinityFunction if it can't guarantee cross-cache collocation?
> 
> -Val
> 
> On Thu, Mar 2, 2017 at 2:41 PM, vkulichenko <valentin.kuliche...@gmail.com 
> <mailto:valentin.kuliche...@gmail.com>> wrote:
> Hi Alex,
> 
> I see your point. Can you please 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.70518.x6.nabble.com/Same-Affinity-For-Same-Key-On-All-Caches-tp10829p11006.html
>  
> <http://apache-ignite-users.70518.x6.nabble.com/Same-Affinity-For-Same-Key-On-All-Caches-tp10829p11006.html>
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
> 

Re: Same Affinity For Same Key On All Caches

[Valentin Kulichenko]

Adding back the dev list.

Folks,

Are there any opinions on the problem discussed here? Do we really need
FairAffinityFunction if it can't guarantee cross-cache collocation?

-Val

On Thu, Mar 2, 2017 at 2:41 PM, vkulichenko <valentin.kuliche...@gmail.com>
wrote:

> Hi Alex,
>
> I see your point. Can you please 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.
> 70518.x6.nabble.com/Same-Affinity-For-Same-Key-On-All-
> Caches-tp10829p11006.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Same Affinity For Same Key On All Caches

[Andrey Mashenkov]

all null:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *previousAssignment:
> nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullassignment:
> [][][][][][][][][][][][][][][][]backups: 1tiers: 2partition set for
> tier:0PartSet [nodeId=5dff841e-c578-476d-8996-39618d39790b, size=0,
> parts=[]]PartSet [nodeId=192f1ddb-89ed-417f-91ae-4cd16b5b1b69, size=0,
> parts=[]]partition set for tier:1PartSet
> [nodeId=5dff841e-c578-476d-8996-39618d39790b, size=0, parts=[]]PartSet
> [nodeId=192f1ddb-89ed-417f-91ae-4cd16b5b1b69, size=0, parts=[]]*
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *Full mapping for partitions: [][][][][][][][][][][][][][][][]*
>
>
> And after that it assign partitions as in round robin:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *Full mapping for partitions:[127.0.0.1, 192.168.1.42][127.0.0.1,
> 192.168.1.28][127.0.0.1, 192.168.1.42][127.0.0.1, 192.168.1.28][127.0.0.1,
> 192.168.1.42][127.0.0.1, 192.168.1.28][127.0.0.1, 192.168.1.42][127.0.0.1,
> 192.168.1.28][127.0.0.1, 192.168.1.42][127.0.0.1, 192.168.1.28][127.0.0.1,
> 192.168.1.42][127.0.0.1, 192.168.1.28][127.0.0.1, 192.168.1.42][127.0.0.1,
> 192.168.1.28][127.0.0.1, 192.168.1.42][127.0.0.1, 192.168.1.28]*
> And after tier 1 assignments:
>
> *Full mapping for partitions:*
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *[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][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][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][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][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][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][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][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 <al...@evam.com> wrote:
>
>> Hi Val,
>>
>> We are using fair affinity function because we want to keep data more
>> balanced among nodes. When I change "new FairAffinityFunction(128)"  with
>> "new RendezvousAffinityFunction(false, 128)" I could not reproduce the
>> problem.
>>
>>
>> On Tue, Feb 28, 2017 at 7:15 AM, vkulichenko <
>> valentin.kuliche...@gmail.com> wrote:
>>
>>> Andrey,
>>>
>>> Is there an explanation for this? If this all is true, it sounds like a
>>> bug
>>> to me, and pretty serious one.
>>>
>>> Alper, what is the reason for using fair affinity function? Do you have
>>> the
>>> same behavior with rendezvous (the default one)?
>>>
>>> -Val
>>>
>>>
>>>
>>> --
>>> View this message in context: http://apache-ignite-users.705
>>> 18.x6.nabble.com/Same-Affinity-For-Same-Key-On-All-Caches-tp
>>> 10829p10933.html
>>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>>
>>
>>
>>
>> --
>> 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>
>>
>
>
>
> --
> 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

Re: Same Affinity For Same Key On All Caches

[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 different caches.

You can find my test code and resuts as attachment.

So is that a bug? Is there a way to force same mappings althought caches
created on different nodes?


On Fri, Feb 24, 2017 at 9:37 AM, Alper Tekinalp  wrote:

> 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
>> guaranteed.
>>
>> D.
>>
>> On Thu, Feb 23, 2017 at 8:09 AM, Andrey Mashenkov <
>> andrey.mashen...@gmail.com> wrote:
>>
>>> 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 
>>> 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
>>> > > > 
>>> > > >
>>> > >
>>> > >
>>> > >
>>> > > --
>>> > > Best regards,
>>> > > Andrey V. Mashenkov
>>> > >
>>> >
>>>
>>>
>>>
>>> --
>>> Best regards,
>>> Andrey V. Mashenkov
>>>
>>
>>
>
>
> --
> 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
> 
>



-- 
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

$ java -Xms1G -Xmx1G -cp "untitled2.jar:EvamEngine_4.3.15/corelib/*" Main 1 10
[18:31:52]__  
[18:31:52]   /  _/ ___/ |/ /  _/_  __/ __/
[18:31:52]  _/ // (7 7// /  / / / _/
[18:31:52] /___/\___/_/|_/___/ /_/ /___/
[18:31:52]
[18:31:52] ver. 1.8.3#20170215-sha1:0a000d89
[18:31:52] 2017 Copyright(C) Apache Software Foundation
[18:31:52]
[18:31:52] Ignite documentation: http://ignite.apache.org
[18:31:52]
[18:31:52] Quiet mode.
[18:31:52]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
"-v" to ignite.{sh|bat}
[18:31:52]
[18:31:52] OS: Mac OS X 10.12.2 x86_64
[18:31:52] VM information: Java(TM) SE Runtime Environment 1.8.0_77-b03 Oracle 
Corporation Java HotSpot(TM) 64-Bit Server VM 25.77-b03
[18:31:53] Configured plugins:
[18:31:53]   ^-- None
[18:31:53]
[18:31:54] Message queue limit is set to 0 which may lead to potential OOMEs 
when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to 
message queues growth on sender and receiver sides.
[18:31:54] Security status [authentication=off, tls/ssl=off]
[18:31:56] Performance suggestions for grid  (fix if possible)
[18:31:56] To disable, set 

Re: Same Affinity For Same Key On All Caches

[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
> guaranteed.
>
> D.
>
> On Thu, Feb 23, 2017 at 8:09 AM, Andrey Mashenkov <
> andrey.mashen...@gmail.com> wrote:
>
>> 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 
>> 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
>> > > > 
>> > > >
>> > >
>> > >
>> > >
>> > > --
>> > > Best regards,
>> > > Andrey V. Mashenkov
>> > >
>> >
>>
>>
>>
>> --
>> Best regards,
>> Andrey V. Mashenkov
>>
>
>


-- 
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

Re: Same Affinity For Same Key On All Caches

[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 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 
> 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
> > > > 
> > > >
> > >
> > >
> > >
> > > --
> > > Best regards,
> > > Andrey V. Mashenkov
> > >
> >
>
>
>
> --
> Best regards,
> Andrey V. Mashenkov
>

Re: Same Affinity For Same Key On All Caches

[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, 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  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
> > > 
> > >
> >
> >
> >
> > --
> > Best regards,
> > Andrey V. Mashenkov
> >
>



-- 
Best regards,
Andrey V. Mashenkov

Re: Same Affinity For Same Key On All Caches

[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,
>
> 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  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
> > 
> >
>
>
>
> --
> Best regards,
> Andrey V. Mashenkov
>

Re: Same Affinity For Same Key On All Caches

[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 be backup for a partition,
that can be an issue.


On Thu, Feb 23, 2017 at 10:44 AM, Alper Tekinalp  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
> 
>



-- 
Best regards,
Andrey V. Mashenkov

Same Affinity For Same Key On All Caches

[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 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