It's possible that it happens because of https://issues.apache.org/jira/browse/IGNITE-13068. We need to scan the entire SQL primary index during startup in case you have at least on query entity configured. As far as I can see it's going to be a part of the Ignite 2.9 release.
-- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
