baimu7 opened a new issue, #12296: URL: https://github.com/apache/ignite/issues/12296
Hello, we are using Ignite 2.15 in our project. In practice, we found that the partition assignment method RendezvousAffinityFunction, which is based on consistent hashing, has an issue with uneven distribution. For example, when assigning partitions to 120 nodes, the number of partitions assigned to each node varies significantly. Is there any way to solve this problem? Alternatively, if our project does not need to consider backups or data migration caused by nodes joining or leaving the cluster, can we simply use a straightforward hash function instead of consistent hashing for partition assignment? If so, what potential issues might arise from this approach? <img width="2300" height="155" alt="Image" src="https://github.com/user-attachments/assets/69556034-159b-4ee5-9b52-3165dc7f8505"; /> [RendezvousAffinityFunctionTest.java](https://github.com/user-attachments/files/21968975/RendezvousAffinityFunctionTest.java) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@ignite.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
