Hi Shawn, Thanks a lot. Managed to stop the commits from client side and no more errors now. Appreciate your timely response. Thank you !
*Regards,* *Reej* On Wed, Aug 25, 2021 at 7:59 PM Shawn Heisey <apa...@elyograg.org> wrote: > On 8/24/2021 10:08 PM, Reej Nayagam wrote: > > Okay, Got your point. But we cannot modify the java code to stop > commits > > for now. So my manager suggests we comment out the auto commit in > > solrconfig instead, We are not sure if that is correct. His point is, let > > us commit every time we index (that is through java passing the commit & > > optimise params) and remove the autocommit config in solrconfig.xml to > > commit every 60000 milliseconds. WIll it be the right approach? > > Don't remove the autoCommit. Frequent hard commits are vital for good > operation -- it flushes data to disk and starts a new transaction log. > Doing it with openSearcher set to false makes it VERY fast. > > Solr ships with autoCommit at 15000 -- up to four times more frequently > than you have it configured ... and it doesn't cause problems for > users. I like to increase that to 60000 just so things are a little bit > less busy, but 15000 would work too. > > The commits that were causing problems for you are the ones sent by your > indexing software, and those commits DO open a new searcher. Opening a > new searcher is the expensive part of a commit ... so your autoCommit is > not a problem. > > > https://lucidworks.com/post/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/ > > (the article says SolrCloud ... but it applies just as much when Solr is > NOT in Cloud mode) > > Thanks, > Shawn > >
