On Fri, May 31, 2013 at 4:11 PM, Jason Hellman <jhell...@innoventsolutions.com> wrote: > Those are default, though autoSoftCommit is commented out by default. > > Keep in mind about the hard commit running every 15 seconds: it is not > updating your searchable data (due to the openSearcher=false setting). In > theory, your data should be searchable due to autoSoftCommit running every 1 > second. Every 15 seconds the hard commit comes along to truncate the > transaction logs and persist the data to lucene segments, but searches are > still being served from a combat ion of the last hard commit with > openSearcher=true plus all the soft committed data in memory. > > At some point it's useful to call a hard commit with openSearcher=true.
Actually, that shouldn't be necessary. A softCommit is essentially like a commit except that files aren't fsync'd (and a new segments descriptor isn't written out). The reopen done on the index reader will certainly use the new segments that have been flushed by the last hard commit (even if openSearcher=false), as well as any non-committed segments caused by other soft commits or the index writer flushing naturally. -Yonik http://lucidworks.com
