Hi, Yes, normally we epxect data to be evenly distributed between nodes. There could be variety of reasons for bad balance: 1) May be you have custom affinity configuration (e.g. *@AffinityKeyMapped*) annotation). 2) May be you load data from store what also may lead to this.
Could you please provide the whole Ignite configuration as well as source code of your keys? Also please explain how do you measure keys distribution. Do you use *org.apache.ignite.cache.affinity.Affinity* interface or something else? Vladimir. On Sat, Mar 19, 2016 at 8:12 PM, kberthelot <[email protected]> wrote: > I've created a partitioned cache with the following configuration: > > cacheConfiguration.setCacheMode(CacheMode.PARTITIONED); > cacheConfiguration.setName(CACHE_NAME); > cacheConfiguration.setRebalanceMode(CacheRebalanceMode.SYNC); > > When I bring up a new node some of the keys get "rebalanced" to the new > node, but the nodes do not end up balanced evenly (the new node often ends > up with only one or very few entries). Should the default behavior be that > the entries are evenly sharded across all nodes, or is there a setting that > forces this behavior? I would expect all the nodes to have close to the > same > number of entries after rebalancing. > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Nodes-not-rebalancing-evenly-tp3589.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
