Yes, every time topology is changed, assignments will be recalculated and data will be rebalanced.
By partitioning mechanisms I meant basically the same that Dmitry was describing before. Ignite automatically distributes cache entries across nodes based on built-in affinity function. This function is pluggable and you are free to create your own, but this task is usually not trivial - I would recommend to do that only if you're absolutely sure that's the only way to go. As a matter of fact, I have never seen a use case where it would be a strong requirement. I also believe that the actual partitioning algorithm (regardless of which one you use) should be abstracted form the application, meaning that the business logic should not depend on it. It sounds like you want to break this abstraction which makes me think that you might go in the wrong direction. But unfortunately I don't think I can help more since you're not ready to disclose details :) -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
