Hi Aaron, > If I bring up the node X, every events as expected, but Now If I start > Node Y, > I still got a lot CacheA and CacheB 's rebalance events. > But Node Y's start or stop should not affect CacheA & CacheB, > their partition never change or rebalance, log after Y started: Yes, I see your point. When a new node joins the cluster the process of 'partition map exchange' is triggered (potentially, some partitions will be moved to a new node) and this the reason why you get CACHE_REBALACE_STARTED/STOPPED events. In your particular case, these messages are redundant. Perhaps, it should be handled on Ignite side...
Thanks! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
