[jira] [Resolved] (IGNITE-4765) Different partition mapping for caches that use Fair Affinity Function

["Valentin Kulichenko (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Valentin Kulichenko resolved IGNITE-4765.
-----------------------------------------
    Resolution: Won't Fix

This will be fixed here: https://issues.apache.org/jira/browse/IGNITE-5836

> Different partition mapping for caches that use Fair Affinity Function
> ----------------------------------------------------------------------
>
>                 Key: IGNITE-4765
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4765
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>            Reporter: Alper Tekinalp
>         Attachments: PartitionDsitributionTest.java
>
>
> Caches created on different topology versions with fair affinity funtion may have different partition mapping. The cause of this problem is fair affinity function calculates partition mappings based on previous assignments. When rebalancing partitions previous assignments for a cache is known and new assignment calculated based on that. But when you create a new cache there is no previous assignments and the calculation is different. 
> Reproduction steps:
> - Start node1
> - Start cache1
> - Start node2
> - Partitions for cache1 will be rebalanced
> - Start cache2
> - Check partition mapping for both cache1 and cache2



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)