I just realized I failed my own reading comprehension :) You have maxDocs, not maxTime for hard commit. Please disregard.
On May 30, 2014, at 1:46 PM, Jason Hellman <jhell...@innoventsolutions.com> wrote: > I’m also not sure I understand the practical purpose of your hard/soft auto > commit settings. You are stating the following: > > Every 10 seconds I want data written to disk, but not be searchable. > Every 15 seconds I want data to be written into memory and searchable. > > I would consider whether your soft commit window is too long, or if you can > lengthen your hard commit period. It’s typical to see hard commits occur > *less* frequently than soft commits. > > > On May 30, 2014, at 11:04 AM, Shawn Heisey <s...@elyograg.org> wrote: > >> On 5/29/2014 9:55 PM, M, Arjun (NSN - IN/Bangalore) wrote: >>> Thanks a lot for your nice explanation.. Now I understood the >>> difference between autoCommit and autoSoftCommit.. Now my config looks like >>> below. >>> >>> <autoCommit> >>> <maxDocs>10000</maxDocs> >>> <openSearcher>false</openSearcher> >>> </autoCommit> >>> >>> <autoSoftCommit> >>> <maxTime>15000</maxTime> >>> </autoSoftCommit> >>> >>> >>> With this now I am getting some other error like this. >>> >>> org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: >>> version conflict for 1401421678039128128000000030383128128 >>> expected=1469497192978841608 actual=1469497212082847746 >> >> This sounds like you are including the _version_ field in your document >> when you index. You probably shouldn't be doing that. Here's what that >> field is for, and how it works: >> >> http://heliosearch.org/solr/optimistic-concurrency/ >> >> Thanks, >> Shawn >> >
