The case you are referring to is a baseline node being offline for a period of time. Like I mentioned before, once this node comes back online it will undergo historical rebalancing to catch on data it missed.
like you said, idle_verify is a tool used to determine if there are inconsistencies between backup and primary, but is not related to the use case presented. See: https://ignite.apache.org/docs/latest/tools/control-script#cluster-should-be-idle-during-idle_verify-check Each node writes to the WAL on its own in order to prevent loss of data. https://ignite.apache.org/docs/latest/persistence/native-persistence.html#checkpointing During the aforementioned historical rebalancing process, the WAL is being used to determine the delta between the data the previously offline node has and what it needs to have. https://www.gridgain.com/docs/latest/developers-guide/historical-rebalancing from the doc: Historical rebalancing relies on the history of updates stored in the write-ahead-log files (WALs) of cluster nodes. The WALs' history must keep updates of all the partitions which deltas need to be rebalanced to a restarted node. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
