From java-user-return-50695-apmail-lucene-java-user-archive=lucene.apache.org@lucene.apache.org Sat Sep 3 21:40:36 2011 Return-Path: X-Original-To: apmail-lucene-java-user-archive@www.apache.org Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BCE3C8F30 for ; Sat, 3 Sep 2011 21:40:36 +0000 (UTC) Received: (qmail 55476 invoked by uid 500); 3 Sep 2011 21:40:34 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 55410 invoked by uid 500); 3 Sep 2011 21:40:33 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 55394 invoked by uid 99); 3 Sep 2011 21:40:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Sep 2011 21:40:33 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of uwe@thetaphi.de designates 188.138.97.18 as permitted sender) Received: from [188.138.97.18] (HELO mail.sd-datasolutions.de) (188.138.97.18) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Sep 2011 21:40:25 +0000 Received: from VEGA (188-193-196-0-dynip.superkabel.de [188.193.196.0]) by mail.sd-datasolutions.de (Postfix) with ESMTPSA id 434C914AA0F0 for ; Sat, 3 Sep 2011 21:40:01 +0000 (UTC) From: "Uwe Schindler" To: References: <4E620B02.E9F9.0090.0@gwava.com> In-Reply-To: <4E620B02.E9F9.0090.0@gwava.com> Subject: RE: Memory issues Date: Sat, 3 Sep 2011 23:41:05 +0200 Message-ID: <002601cc6a82$2fa46f20$8eed4d60$@thetaphi.de> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-index: AQFoHKeTBGn5M5yfSsVG+GjzexmEJZYEyryQ Content-language: de X-Virus-Checked: Checked by ClamAV on apache.org There is no difference between 2.9 and 3.0, ist exactly the same code with only Java 5 specific API modifications and removal of deprecated methods. The issue you have seems to be that maybe your index have grown beyond some limits of your JVM. Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: uwe@thetaphi.de > -----Original Message----- > From: Michael Bell [mailto:mjb@gwava.com] > Sent: Saturday, September 03, 2011 8:10 PM > To: java-user@lucene.apache.org > Subject: Memory issues > > Ok, one customer of ours insists on running a Really Big Single Server Lucene > index. > > To be exact, there are about 300 million documents. This is running on a 64 bit > JVM/64 bit OS with 24 GB(!) RAM allocated. > > Until very recently all was well. We then updated then in program version, > which updated lucene 2.93 to lucene 3.02 > > Now, their searches are working fine IF you do not SORT the results. If you do > SORT, you get stuff like > > 2011-08-30 13:01:31,489 [TP-Processor8] ERROR > com.gwava.utils.ServerErrorHandlerStrategy - reportError: nastybadthing :: > com.gwava.indexing.lucene.internal.LuceneSearchController.performSearchOp > eration:229 :: EXCEPTION : java.lang.OutOfMemoryError: Requested array size > exceeds VM limit java.lang.OutOfMemoryError: Requested array size exceeds > VM limit at > org.apache.lucene.search.FieldCacheImpl$StringIndexCache.createValue(Field > CacheImpl.java:624) > at > org.apache.lucene.search.FieldCacheImpl$Cache.get(FieldCacheImpl.java:183) > at > org.apache.lucene.search.FieldCacheImpl.getStringIndex(FieldCacheImpl.java:6 > 11) > at > org.apache.lucene.search.FieldComparator$StringOrdValComparator.setNextR > eader(FieldComparator.java:805) > at > org.apache.lucene.search.TopFieldCollector$OneComparatorNonScoringCollect > or.setNextReader(TopFieldCollector.java:96) > at org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:209) > at org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:199) > at org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:177) > at org.apache.lucene.search.Searcher.search(Searcher.java:49) > at > com.gwava.indexing.lucene.internal.LuceneSearchController.performSearchOp > eration(LuceneSearchController.java:223) > at > > Looking at the sort class, the api docs appear to say it would create an element > of 1.2 billion items (4*300m). Is this correct? Is the issue going beyond signed > int32 limits of an array ( 2 billion items) or is it really a memory issue? How > best to diagnose? > > Thanks > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org > For additional commands, e-mail: java-user-help@lucene.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org