Hi, Looks like the error message is truncated. Could you please re-send it or attach the full log file? PartitionsEvictManager is part of rebalancing routine and it clears local data before demanding it from other nodes. Also I see the following JIRA https://issues.apache.org/jira/browse/IGNITE-11974 From: maxi628 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 ignite and starting it again, without ever changing the baseline topology, it can take 2 minutes to restart the container. The node joins the topology just fine but takes a long time to start serving traffic. Checking the logs I've found that there are several lines like this ones here: So for some reason after booting it starts a process called PartitionsEvictManager, which can take a lot of time. What is the intended functionality behind PartitionsEvictManager? It is something that we should expect? This is a problem because a rolling restart of all nodes in a cluster can take up to a day. Thanks. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/ |
- Ignite rebalancing when a server is rebooted w/ persistan... maxi628
- RE: Ignite rebalancing when a server is rebooted w/ ... Alexandr Shapkin
