Hi Val, >From the server logs, we could actually see that the re-balancing was complete.
Logs for your reference - [17:56:53,055][INFO][sys-#35%null%][GridDhtPartitionDemander] <TEST_CACHE> Starting rebalancing [cache=TEST_CACHE, mode=ASYNC, fromNode=81facbbd-40be-4a21-b018-1544aab1a3ba, partitionsCount=11, topology=AffinityTopologyVersion [topVer=93, minorTopVer=0], updateSeq=1] [17:58:51,936][INFO][sys-#37%null%][GridDhtPartitionDemander] <TEST_CACHE> Completed rebalancing [cache=TEST_CACHE, fromNode=81facbbd-40be-4a21-b018-1544aab1a3ba, topology=AffinityTopologyVersion [topVer=93, minorTopVer=0], time=118884 ms] Soon after this, for some time, the SQL query execution was very slow. So we were under the impression that the indexes are not yet created. It would be great if you could provide some insight on the following - 1) Is the index creation part of re-balancing process ? 2) Details on ASYNC re-balancing mode. >From Docs, we see that for ASYNC mode - Distributed caches will start immediately and will load all necessary data from other available grid nodes in the background. In this case, will the data (SQL Query Result) be consistent? Also, how about the index creation ? Thanks, Ganesh -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Issue-with-SQL-Query-Performance-Post-Rebalance-Operation-tp9308p9389.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
