Alexandre: It Depends (tm) of course. It all hinges on the setting in <autocommit>, whether <openSearcher> is true or false.
In the former case, you, well, open a new searcher. In the latter you don't. I agree, though, this is all tangential to the memory consumption issue since the RAM buffer will be flushed regardless of these settings. FWIW, Erick On Fri, Sep 5, 2014 at 7:11 AM, Alexandre Rafalovitch <arafa...@gmail.com> wrote: > On Fri, Sep 5, 2014 at 9:55 AM, Mikhail Khludnev > <mkhlud...@griddynamics.com> wrote: >>> Why do one big commit? You could do hard commits along the way but keep >>> searcher open and not see the changes until the end. >>> >> >> Alexandre, >> I don't think it's can happen in solr-user list, next search pickups the >> new searcher. > > Why not? Isn't that what the Solr example configuration doing at: > https://github.com/apache/lucene-solr/blob/lucene_solr_4_10_0/solr/example/solr/collection1/conf/solrconfig.xml#L386 > ? > Hard commit does not reopen the searcher. The soft commit does > (further down), but that can be disabled to get the effect I am > proposing. > > What am I missing? > > Regards, > Alex. > > Personal: http://www.outerthoughts.com/ and @arafalov > Solr resources and newsletter: http://www.solr-start.com/ and @solrstart > Solr popularizers community: https://www.linkedin.com/groups?gid=6713853
