Hello!
Data distribution will only be uniform if affinity key distribution is
uniform, and may still go +/- 10% between nodes.
Regards,
--
Ilya Kasnacheev
чт, 18 июн. 2020 г. в 09:41, VincentCE :
> Thank you for your answer. We are aware of that our approach is not the
> clean
> one as the
Thank you for your answer. We are aware of that our approach is not the clean
one as the one with explicitly defined affinity keys would be. But still for
the sake of data distribution defining affinityKeys, in this example this
would be cacheName/key for a given key, should be equivalent to
Hi,
see:
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/affinity/Affinity.html
Can you see the key to partition mappings:
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/affinity/Affinity.html#mapKeyToPrimaryAndBackups-K-
to see what
In our project a lot of data records share the same keys, i.e. a given key
might exist in several of our caches (with different values though). We
suspect that this is the reason for our non-uniform data-distribution over
the cluster-nodes that we are facing since all data-records that share the