ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Goncharuk <alexey.goncha...@gmail.com>
Subject Re: Same Affinity For Same Key On All Caches
Date Thu, 02 Mar 2017 08:06:18 GMT
This does not look like a bug to me. Rendezvous affinity function is
stateless, while FairAffinityFunction relies on the previous partition
distribution among nodes, thus it IS stateful. The partition distribution
would be the same if caches were created on the same cluster topology and
then a sequence of topology changes was applied.

2017-03-02 0:14 GMT+03:00 vkulichenko <valentin.kulichenko@gmail.com>:

> 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.

View raw message