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
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/
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
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
Hi,
I have following case.
I have around 1 subscriptions. Each subscription has data varying from
1 to 10 million.
Currently the affinity key is set on subscriptionId.
e.g:
Subscription1: 2 million rows
Subscription2: 10 million rows
Subscription3: 50 million rows
Subscription5: 30 million
