Re: Ignite rebalancing when a server is rebooted w/ persistance enabled.

The cluster was almost idle. It didn't receive lots of updates while that node was down. Is there any way to confirm which of those two options you mentioned was executed? Is there any way to configure a threshold to choose one of those two options? -- Sent from:

Re: Ignite rebalancing when a server is rebooted w/ persistance enabled.

Hello! While the node was down, the partitions that it previously owned had their data updated. At this point we only have two options: - Throw out existing partitions and rebalance them. AFAIK it involves WAL so it will take some time. I have heard that if you wipe node's persistence then it

RE: Ignite rebalancing when a server is rebooted w/ persistance enabled.

Sorry, I'm attaching the log here ignite_eviction.log I've read https://issues.apache.org/jira/browse/IGNITE-11974 and the thing is, this isn't an infinite loop. The remainingPartsToEvict=$something starts going

RE: Ignite rebalancing when a server is rebooted w/ persistance enabled.

-11974  From: maxi628Sent: Thursday, January 14, 2021 12:16 AMTo: user@ignite.apache.orgSubject: Ignite rebalancing when a server is rebooted w/ persistance enabled. Hello everyone. I have several ignite clusters with version 2.7.6 and persistence enabled.I have a 3 caches on every cluster, with 10M

Ignite rebalancing when a server is rebooted w/ persistance enabled.

Hello everyone. I have several ignite clusters with version 2.7.6 and persistence enabled. I have a 3 caches on every cluster, with 10M~ records each. Sometimes when I reboot a node, it takes a lot of time to boot, it can be hours. With rebooting I mean stopping the container that's running