Re: Cache not rebalanced after one node is restarted

The Ignite 2.5 was released and can be downloaded from the Ignite website: https://ignite.apache.org/download.html D. On Wed, May 30, 2018 at 6:34 AM, Stanislav Lukyanov wrote: > Most likely you've run into this bug: > https://issues.apache.org/jira/browse/IGNITE-8210 > > It was fixed in 2.5,

Re: Cache not rebalanced after one node is restarted

Most likely you've run into this bug: https://issues.apache.org/jira/browse/IGNITE-8210 It was fixed in 2.5, try updating to that version. Thanks, Stan -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cache not rebalanced after one node is restarted

Has anyone some advice for this situation? Thanks. On Mon, May 21, 2018, 21:29 Vadym Vasiuk wrote: > HI All, > > I also noticed that if I bounce one of two nodes and data is then > distributed as I described (one node has all the PRIMARY entries and second > one has only

Re: Cache not rebalanced after one node is restarted

HI All, I also noticed that if I bounce one of two nodes and data is then distributed as I described (one node has all the PRIMARY entries and second one has only BACKUP entries) - after I restart second node - data is again distributed normally. But what if I dont want to restart all nodes to

Re: Cache not rebalanced after one node is restarted

Hi Stanislav, Yes persistence is enabled and version is 2.4. Have tried to update topology after one node restart with below code from client: Collection nodes = ignite.cluster().forServers.nodes(); ignite.cluster().setBaselineTopology(nodes); And after that I still have all primary entries

RE: Cache not rebalanced after one node is restarted

Hi, Do you have native persistence enabled? What is your Ignite version? If the Ignite version is 2.4+ and you have persistence, the problem is most likely with baseline topology. You need to make sure that the restarted node is in the baseline for the rebalance to happen, either by keeping

Re: Cache not rebalanced after one node is restarted

Hi, It is possible, you put too few data that belongs to 2 partitions (total partition is 1024 by default) and after restart you got different partition distribution for 2 nodes. Please take a look at how affinity function works [1]. [1]