waitFlush=true means that the commit HTTP call waits until everything is sent to disk before it returns. waitSearcher=true means that the commit HTTP call waits until Solr has reloaded the index and is ready to search against it. (For more, study Solr warming up.)
Both of these mean that the HTTP call (or curl program or Solrj program) that started the commit, waits until it is done. Other processes doing searches against the index are not blocked. However, the commit may have so much disk activity that the other searches do not proceeed very fast. They are not completely blocked. The commit will take as long as it takes, and your results will appear after that. If you want to time that, use waitFlush=true&waitSearcher=true. On Fri, Mar 5, 2010 at 9:39 PM, gunjan_versata <gunjanga...@gmail.com> wrote: > > But can anyone explain me the use of these parameters.. I have read upon it.. > what i could not understand was.. if can i set both the params to false, > after how much time will my changes start reflecting? > > -- > View this message in context: > http://old.nabble.com/SolrJ-commit-options-tp27714405p27802041.html > Sent from the Solr - User mailing list archive at Nabble.com. > > -- Lance Norskog goks...@gmail.com
