Hi Ganesh, 1. Index is updated each time an entry is updated. It doesn't actually matter, what initiates the update - put() operation, read-through, rebalancing or anything else. Thus, once rebalancing is completed, all indexes are up to date. 2. Rebalancing mode only controls the use of public API on a node that joins topology. With ASYNC mode you will be able to use public API concurrently with rebalancing, however with SYNC mode any cache operation will block until rebalancing is completed. This however does not affect nodes that already exist.
-Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Issue-with-SQL-Query-Performance-Post-Rebalance-Operation-tp9308p9495.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
