Hi I'm working on an Ignite project where all the data is partitioned based on field partition-id and it is set as affinitykeyfield. We are running 5 ignite servers on 5 machines which have identical hardware and ignite heap settings/java options. Our data has overall 5 partition-ids(1-5) . But when we insert same number of records for each partition id the data is not spreading equally among all ignite servers. For example when we insert 5 records of each with partition id 1-5 , Its expected that each server node has one record. But the distribution is different. I used Affinity.mapPartitionToNode() function to see how partitions are mapped to nodes and we see the following mapping:
partiton-id : 1 [192.168.10.155] partiton-id : 2 [192.168.10.155] partiton-id : 3 [192.168.10.155] partiton-id : 4 [192.168.10.153] partiton-id : 5 [192.168.10.155] And our ignite server nodes are : 1. 192.168.10.152 2. 192.168.10.153 3. 192.168.10.154 4. 192.168.10.155 5. 192.168.10.157 We even changed the number of partitions as 5 using RendezvousAffinityFunction But still the partition to node mapping was exactly same as without RendezvousAffinityFunction(the above mapping). Our data is almost evenly distributed among the partition ids hence we require even partition to node distribution. How can we achieve that ? We do not want to mess with any ignite default properties except the partition to node mapping. We will also be using backups. Also why is the default partition to node mapping not balanced ? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
