Return-Path: X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1ECA510090 for ; Thu, 29 May 2014 13:53:28 +0000 (UTC) Received: (qmail 17707 invoked by uid 500); 29 May 2014 13:53:25 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 17631 invoked by uid 500); 29 May 2014 13:53:25 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 17623 invoked by uid 99); 29 May 2014 13:53:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 May 2014 13:53:25 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of arjun.m@nsn.com designates 93.183.12.32 as permitted sender) Received: from [93.183.12.32] (HELO demumfd001.nsn-inter.net) (93.183.12.32) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 May 2014 13:53:19 +0000 Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.14.3/8.14.3) with ESMTP id s4TDqbqk022641 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 29 May 2014 13:52:37 GMT Received: from SGSIHTC003.nsn-intra.net ([10.159.225.20]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id s4TDqMl3030146 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Thu, 29 May 2014 15:52:37 +0200 Received: from SGSIMBX002.nsn-intra.net ([169.254.2.62]) by SGSIHTC003.nsn-intra.net ([10.159.225.20]) with mapi id 14.03.0181.006; Thu, 29 May 2014 21:52:23 +0800 From: "M, Arjun (NSN - IN/Bangalore)" To: "solr-user@lucene.apache.org" Subject: RE: Error enquiry- exceeded limit of maxWarmingSearchers=2 Thread-Topic: Error enquiry- exceeded limit of maxWarmingSearchers=2 Thread-Index: AQHPeigKXDyHWZTUSEefOkIIBOh/3JtU6RqAgADVDmD//7J5gIAB20/w//++ZoCAAIttUA== Date: Thu, 29 May 2014 13:52:23 +0000 Message-ID: References: <8045fe9813d14dfc4ac7eff2269034fe.squirrel@admin.elyograg.org> <5385DF25.1080909@elyograg.org> <538736D5.8040401@elyograg.org> In-Reply-To: <538736D5.8040401@elyograg.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.159.225.111] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-purgate-type: clean X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de X-purgate: clean X-purgate: This mail is considered clean (visit http://www.eleven.de for further information) X-purgate-size: 2962 X-purgate-ID: 151667::1401371557-00001326-CFBA4DBF/0/0 X-Virus-Checked: Checked by ClamAV on apache.org Thanks Shawn... Just one more question.. Can both autoCommit and autoSoftCommit be enabled? If both are enabled, whi= ch one takes precedence? Thanks & Regards, Arjun M -----Original Message----- From: ext Shawn Heisey [mailto:solr@elyograg.org]=20 Sent: Thursday, May 29, 2014 7:02 PM To: solr-user@lucene.apache.org Subject: Re: Error enquiry- exceeded limit of maxWarmingSearchers=3D2 On 5/29/2014 4:18 AM, M, Arjun (NSN - IN/Bangalore) wrote: > Thanks for your valuable inputs... Find below my code and config in solr= config.xml. Index update is successful but I am not able to see any data fr= om solr admin console. What could be the issue? Any help here is highly app= reciated. >=20 > I can see the data in the solr admin gui after tomcat restart(solr is ru= nning in tomcat in my case) >=20 > private void addToSolr(List c) throws SolrServerExcept= ion, IOException { > if (!c.isEmpty()) { > try { > =20 > =20 > solr.add(c); > logger.info("Commit size after Add=3D" + c.size()); > =20 > } finally { > //renew lock > } > } > } >=20 > autoCommit config in solrconfig.xml > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > =20 > ${solr.autoCommit.maxTime:15000} > 10000 > false=20 > >=20 > =20 > ${solr.autoSoftCommit.maxTime:-1}=20 > The code snippet does not include a commit. I am not really clear on what using a value of -1 would do on maxTime here. I suspect that it efectively disables autoSoftCommit. If that's the case, then there is nothing at all in your code or your config that will open a new searcher -- that option is set to false in your autoCommit. If you want Solr to automatically do commits to make documents visible, I think you should configure a maxTime value for autoSoftCommit, and make it as long as you can possibly stand to not have new documents available. Then you won't have to worry about commits in your code at all. > Few more questions..=20 >=20 > 2) If I use solrServer.add(,), should I do solrSe= rver.commit() also No. The commitWithin would do a soft commit for you once that much time has elapsed since indexing started (or the last commit with openSearcher=3Dtrue), so you would not need to do a commit(). My opinion is that you should not combine manual commits with autoSoftCommit. Depending on exactly what your needs are, you might want to use commitWithin, and have autoSoftCommit as a last guarantee against errors in your indexing process. Thanks, Shawn