Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: unknown (nike.apache.org: error in processing during lookup of
 siraj@jobdiva.com)
Message-ID: <4B314F79.1050909@jobdiva.com>
Date: Tue, 22 Dec 2009 18:00:09 -0500
From: Siraj Haider <siraj@jobdiva.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "java-user@lucene.apache.org" <java-user@lucene.apache.org>
Subject: Re: Lucene going non-responsive under heavy load
References: <4B3145D5.2040708@jobdiva.com>
 <9AF96C3A32064421A29AAAA5143D07DE@VEGA>
In-Reply-To: <9AF96C3A32064421A29AAAA5143D07DE@VEGA>
Content-Type: multipart/alternative;
	boundary="------------010706050202070707010904"

--------------010706050202070707010904
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

Hi Uwe,
Following are the info:
Java VM: "1.6.0_05"
Java Options:  -server -Xms512m -Xmx2048m
We are not using any specific GC.

regards
-siraj

Uwe Schindler wrote:
> If it suddenly gets unresponsive, you may have a GC (garbage collector)
> problem. Can you post your Java options, Java VM version, max heap and so
> on. Maybe you are doing some strange things.
>
> For us the best GC to use (we have Java 1.5) was the "Parallel New GC" /
> "The Concurrent Low Pause Collector", here are some of our options that
> helped solving the problem: -XX:+UseConcMarkSweepGC -XX:+UseParNewGC. You
> may also read Mark Millers Blog post:
>
> http://www.lucidimagination.com/blog/2009/09/19/java-garbage-collection-boot
> -camp-draft/
>
> Uwe
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: uwe@thetaphi.de
>
>   
>> -----Original Message-----
>> From: Siraj Haider [mailto:siraj@jobdiva.com]
>> Sent: Tuesday, December 22, 2009 11:19 PM
>> To: java-user@lucene.apache.org
>> Subject: Lucene going non-responsive under heavy load
>>
>> Hello guys,
>> We have a dilemma on a few of our lucene machines.  We have a tomcat
>> running our servlets for searching and indexing on each of these
>> machines.  Its a live index where documents are being added to index
>> while online searches are also being served at the same time.  Indexing
>> happens every 5 minutes and if there are new documents added, the index
>> gets reopend.  For most of the times the performance is very good, but
>> under heavy load of searches, the machine goes non-responsive.  We can
>> still telnet to machine and see that cpu-wise its not bad, but I/O seems
>> to be a problem.  Is there anything we might be doing to cause it or
>> anything that we can do to avoid it.  I know I did not provide a lot of
>> information about how we are indexing and searching but I will answer
>> any question anyone might have.
>>
>> thanks in advance
>> -siraj
>>
>> ---------------------------------------------------------------------
>> 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
>
>   


--------------010706050202070707010904--