On Fri, Jul 24, 2015 at 2:40 PM, Amit Jain <[email protected]> wrote: >> Well that would work for a single node deployment when TarMK is used >> but would still have a lag as based on frequency of AsyncIndexer which >> we are seeing is having delays of upto 10-20 sec and may vary. For >> cluster where indexing is happening on a single node it cannot be >> used. >> > > But wouldn't that be a problem for the in-memory index also?
Nopes. The in memory index would be managed on each cluster node and has visibility to *local* changes happening on that cluster node. So it would certainly not provide a cluster wide real time search. But it help in those cases where user is performing changes via his session established with a single cluster node and is not able to see affect of his latest changes. We have seen some problems reported so far, so we can wait further to see if the problem affect more usecases and then decide to invest in such a feature! Chetan Mehrotra
