Re: Customized affinity function

2018-04-19 Thread vkulichenko
Statistically it's very unlikely that all big subscriptions (or many of them) will end up together. So I would check if there is an issue first and go from there. Technically you can implement your own AffinityFunction to customize distribution. But that's not a trivial task as you will have to

Re: Customized affinity function

2018-04-19 Thread Prasad Bhalerao
Hi Val, Out 1 subscriptions, only 10-20 subscriptions are very big. I just want to make sure that these big subscriptions do not land up in partitions which are located on same node. On Thu, Apr 12, 2018 at 7:44 AM, vkulichenko wrote: > Prasad, > > Are

Re: Customized affinity function

2018-04-11 Thread vkulichenko
Prasad, Are you collocating data by subscription? Do you have any actual issue with data distribution? With 1 subscriptions, I don't see why would you have one with default settings. -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Customized affinity function

2018-04-11 Thread aealexsandrov
Hi Prasad, Affinity function does not directly map keys to nodes, it maps keys to partitions. So it takes care about entities balance between nodes. To read more please take a look here: https://apacheignite.readme.io/docs/affinity-collocation#affinity-function In case if for every subscriber

Re: Customized affinity function

2018-04-11 Thread Mikael
Hi! The |@AffinityKeyMapped annotation can be used on a field or a method, so you can have a method returning anything you want (based on size), would that not work ?| |Mikael | Den 2018-04-11 kl. 07:59, skrev Prasad Bhalerao: Hi, I have following case. I have around 1