Hello,
I've tried in sample project and worked as expected. In my original case I
had updated records in database using arbitrary partition ids. I had
misunderstood. I should have updated records according to affinity function.
Thank you
Regards,
Serdar
On 20 March 2018 at 16:57, slava.koptilin
Hello serdar,
Well, I just checked your project and it seems I found the root cause of
that behavior.
UserInfoGenerator uses wrong logic in order to generate the partitionId.
The partitionId must be equal the value that is returned by corresponding
affinity function, i.e.
partitionId =
I have asked a question on stackoverflow.com.
https://stackoverflow.com/questions/49145540/why-ignite-does-not-load-all-records-into-cache-when-server-node-count-increased/49155857?noredirect=1#comment85629822_49155857
@Dmitriy asked for a reproducer example. I had supplied an example on
github.
