Hi!

Garbage collection is an issue of the underlying JVM. You may use
–XX:+PrintGCDetails as an argument to your JVM in order to collect
details of the garbage collection. If you also use the parameter
–XX:+PrintGCTimeStamps you get the time stamps of the garbage
collection.

For further information you may want to refer to the paper

<http://java.sun.com/j2se/reference/whitepapers/memorymanagement_whitepaper.pdf>

which points you to a few other utilities related to GC.

Best,

Sven Maurmann

--On Mittwoch, 13. Januar 2010 18:03 +0000 Frederico Azeiteiro <frederico.azeite...@cision.com> wrote:

The hanging didn't happen again since yesterday. I never run out of space
again. This is still a dev environment, so the number of searches is very
low. Maybe I'm just lucky...

Where can I see the garbage collection info?

-----Original Message-----
From: Marc Des Garets [mailto:marc.desgar...@192.com]
Sent: quarta-feira, 13 de Janeiro de 2010 17:20
To: solr-user@lucene.apache.org
Subject: RE: Problem comitting on 40GB index

Just curious, have you checked if the hanging you are experiencing is not
garbage collection related?

-----Original Message-----
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: 13 January 2010 13:33
To: solr-user@lucene.apache.org
Subject: Re: Problem comitting on 40GB index

That's my understanding...... But fortunately disk space is cheap <G>....


On Wed, Jan 13, 2010 at 5:01 AM, Frederico Azeiteiro <
frederico.azeite...@cision.com> wrote:

Sorry, my bad... I replied to a current mailing list message only
changing the subject... Didn't know about this " Hijacking" problem.
Will not happen again.

Just for close this issue, if I understand correctly, for an index of
40G, I will need, for running an optimize:
- 40G if all activity on index is stopped
- 80G if index is being searched...)
- 120G if index is being searched and if a commit is performed.

Is this correct?

Thanks.
Frederico
-----Original Message-----
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: terça-feira, 12 de Janeiro de 2010 19:18
To: solr-user@lucene.apache.org
Subject: Re: Problem comitting on 40GB index

Huh?

On Tue, Jan 12, 2010 at 2:00 PM, Chris Hostetter
<hossman_luc...@fucit.org>wrote:

>
> : Subject: Problem comitting on 40GB index
> : In-Reply-To: <
> 7a9c48b51001120345h5a57dbd4o8a8a39fc4a98a...@mail.gmail.com>
>
> http://people.apache.org/~hossman/#threadhijack
> Thread Hijacking on Mailing Lists
>
> When starting a new discussion on a mailing list, please do not reply
> to an existing message, instead start a fresh email.  Even if you
> change the subject line of your email, other mail headers still track
> which thread you replied to and your question is "hidden" in that
> thread and gets less attention.   It makes following discussions in
> the mailing list archives particularly difficult.
> See Also:  http://en.wikipedia.org/wiki/User:DonDiego/Thread_hijacking
>
>
>
> -Hoss
>
>

----------------------------------------------------------
This transmission is strictly confidential, possibly legally privileged,
and intended solely for the  addressee.  Any views or opinions expressed
within it are those of the author and do not necessarily  represent those
of 192.com, i-CD Publishing (UK) Ltd or any of it's subsidiary companies.
If you  are not the intended recipient then you must not disclose, copy
or take any action in reliance of this  transmission. If you have
received this transmission in error, please notify the sender as soon as
possible.  No employee or agent is authorised to conclude any binding
agreement on behalf of  i-CD Publishing (UK) Ltd with another party by
email without express written confirmation by an  authorised employee of
the Company. http://www.192.com (Tel: 08000 192 192).  i-CD Publishing
(UK) Ltd  is incorporated in England and Wales, company number 3148549,
VAT No. GB 673128728.

Reply via email to