Thanks, Shawn & Jack. I will go with the wiki and use autoCommit with openSearcher set to false.
On Wed, Jun 26, 2013 at 10:23 AM, Jack Krupansky <j...@basetechnology.com>wrote: > You need to do occasional hard commits, otherwise the update log just > grows and grows and gets replayed on each server start. > > -- Jack Krupansky > > -----Original Message----- From: Arun Rangarajan > Sent: Wednesday, June 26, 2013 1:18 PM > To: solr-user@lucene.apache.org > Subject: Solr 4.2.1 - master taking long time to respond after tomcat > restart > > > Upgraded from Solr 3.6.1 to 4.2.1. Since we wanted to use atomic updates, > we enabled updateLog and made the few unstored int and boolean fields as > "stored". We have a single master and a single slave and all the queries go > only to the slave. We make only max. 50 atomic update requests/hour to the > master. > > Noticing that on restarting tomcat, the master Solr server takes several > minutes to respond. This was not happening in 3.6.1. The slave is > responding as quickly as before after restarting tomcat. Any ideas why only > master would take this long? >
