lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn Heisey <>
Subject Re: SolrJ commit with openSearcher=false
Date Tue, 31 Mar 2015 15:39:34 GMT
On 3/31/2015 2:56 AM, vidit.asthana wrote:
> Thanks for reply Shawn. I will try it out.
> The reason that I am forced to do a hard commit through code is to handle a
> problem I am facing with transaction logs.
> I am forced to delete tlogs manually at regular interval and hence I want to
> issue a hard commit before deleting them to ensure that no data loss happens
> in case of node failure.
> I have explained the issue in detail in another thread -
> If you can provide me some help in finding the fix for the issue, then it
> would be a huge help for me. 

The first thing I would try is to set up autoCommit with a maxTime of
300000 (five minutes) and openSearcher set to false, as shown in the
comments of the the example solrconfig.xml, although that example may
have a value of 15000 (15 seconds).  If that doesn't bring your
transaction logs under control, then you definitely are facing an
unusual situation or a bug where old and outdated transaction logs are
not being automatically deleted.  If it does appear that you've got a
bug, one of the first steps I would take is upgrading from 4.10.0 to
4.10.4 - it should be a drop-in replacement of your .war file and any
contrib jars, and I would delete the extracted version of the war before

Is your data directory on a network filesystem, like NFS or SMB?  That
can sometimes cause weird problems with Solr.

Are you seeing any ERROR or WARN entries in your solr log?


View raw message