Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of arunrangarajan@gmail.com
 designates 209.85.212.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <F49D7D27804F4DF0BE9A50F2BEA2B0E0@JackKrupansky>
References: 
 <CAOnbPhSudU+Pv1vUPM1Wtw_oGT2oRG_LSwDAKECV1-qYdtrtkg@mail.gmail.com>
 <F49D7D27804F4DF0BE9A50F2BEA2B0E0@JackKrupansky>
From: Arun Rangarajan <arunrangarajan@gmail.com>
Date: Wed, 26 Jun 2013 13:03:24 -0700
Message-ID: 
 <CAOnbPhSUgriGg1TcfYtC2n2W3Ah4P6P2Px7X+vPqYex7d+60MQ@mail.gmail.com>
Subject: Re: Solr 4.2.1 - master taking long time to respond after tomcat
 restart
To: solr-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=047d7b5d352891b9f504e014240f

--047d7b5d352891b9f504e014240f
Content-Type: text/plain; charset=ISO-8859-1

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 <jack@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?
>

--047d7b5d352891b9f504e014240f--