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. This will essentially set the state of all searchable data to the segment data from Lucene. Also, the 15 second default isn't intended to be a one-size-fits-all policy. You need to find some good balancer here and testing this out with simulated load is the right way to do this. Others reading this thread may be able to provide better empirical or anecdotal suggestions to you on settings, but be sure to test! On May 31, 2013, at 12:14 PM, ltenny <lte...@gmail.com> wrote: > <autoCommit> > <maxTime>15000</maxTime> > <openSearcher>false</openSearcher> > </autoCommit> > > <autoSoftCommit> > <maxTime>1000</maxTime> > </autoSoftCommit> > > > I think these are close to the default values...not sure if I changed them. > These mean a hard commit every 15 seconds...right? Seems sort of reasonable > since we get a few hundred doc inserts in 15 seconds. Not sure...any advice > is very welcome. > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Getting-tons-of-EofException-with-jetty-SolrCloud-tp4067427p4067433.html > Sent from the Solr - User mailing list archive at Nabble.com.
