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 your distribution look like. you can also see how these same partitions are spread among the nodes. Can you use the mapPartitionsToNodes: https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/affinity/Affinity.html#mapPartitionsToNodes-java.util.Collection- You can look at how partitions are mapped to nodes here: https://github.com/andyglick/apache-ignite/blob/c864fe443284508c7eb1d2341d9fdc2a5a844c45/modules/core/src/main/java/org/apache/ignite/cache/affinity/rendezvous/RendezvousAffinityFunction.java#L497 In general, it is not a good idea to modify the partition function in order to create a pseudo key for partition assignments. This creates dependencies that are hard to untangle later on. Best to work on the level of caches/keys, and use an alternate key for storage. Look into affinity collocation to see if it helps your use case:https://apacheignite.readme.io/docs/affinity-collocation#collocate-data-with-data Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
