Hi. I created a bug ticket for that: https://issues.apache.org/jira/browse/IGNITE-4765
Val, the problem here 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. On Thu, Mar 2, 2017 at 12:14 AM, vkulichenko <[email protected]> wrote: > Andrew, > > Yes, I believe it's a bug, let's create a ticket. > > Do you have any idea why this happens? The function doesn't have any state, > so I don't see any difference between two its instances on same node for > different caches, and two instances on different nodes for the same cache. > This makes me think that mapping inconsistency can occur in the latter case > as well, and if so, it's a very critical issue. > > -Val > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Same-Affinity-For-Same-Key-On-All- > Caches-tp10829p10979.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Alper Tekinalp Software Developer Evam Streaming Analytics Atatürk Mah. Turgut Özal Bulv. Gardenya 5 Plaza K:6 Ataşehir 34758 İSTANBUL Tel: +90 216 455 01 53 Fax: +90 216 455 01 54 www.evam.com.tr <http://www.evam.com>
