Thanks Shawn, may be this is a silly question, but I looked around and didn't find an answer... Well, could I update solrconfig.xml for the collection while the instances are running or should I restart the cluster/reload the cores?
On Sun, May 24, 2015 at 5:07 AM, Shawn Heisey <apa...@elyograg.org> wrote: > On 5/23/2015 8:56 PM, Vincenzo D'Amore wrote: > > looking at tlog size I see there are many collection that have keep more > > than 1GB of space. > > Tlog are growing and the code that adds new documents never does an hard > > commit. > > > > The question is must I fix the code that update the collections or can I > do > > an hard commit externally using collection api or via admin console? > > I strongly recommend that you configure autoCommit in your > solrconfig.xml with openSearcher set to false. > > I will usually recommend an interval of 300000 (five minutes) but others > recommend an interval of 15000 (15 seconds). This kind of autoCommit > generally does happen very quickly, but my philosophy is to keep the > impact of any commit as low as possible ... which means doing them as > infrequently as possible. > > The tradeoff on the autoCommit interval is the size of each individual > transaction log. If you are indexing documents very quickly, you > probably want a shorter interval. > > The example autoCommit config that you can find on the following wiki > page also has maxDocs ... it's up to you whether you include that part > of the config. > > > http://wiki.apache.org/solr/SolrPerformanceProblems#Slow_startup_due_to_the_transaction_log > > Thanks, > Shawn > >
