Hello everyone!
Here are the conclusions we got after digging more into the problem,
maybe they help someone:
1) Filling of the hard-drive was not due to java 64, this was
coincidentally.
2) The intermediate files Yonik talked about (*.f*) were present because
the indexing process was mergin
Thanks everyone for the answers!
I'm experimenting with your suggestions, I will let you know if
something interesting pops up.
roxana
1) make sure the failure was due to an OutOfMemory exception and not
something else.
2) if you have enough memory, increase the max JVM heap size (-Xmx)
3) if
t; I would like to use it.. but I never ever put beta packages in
> procution.. but then again.. I'm always dealing with Microsoft :)
>
> Tom
>
> -Original Message-
> From: Yonik Seeley [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 21, 2005 9:28 AM
> To: jav
ssage-
From: Yonik Seeley [mailto:[EMAIL PROTECTED]
Sent: Friday, October 21, 2005 9:28 AM
To: java-user@lucene.apache.org
Subject: Re: java on 64 bits
1) make sure the failure was due to an OutOfMemory exception and not
something else.
2) if you have enough memory, increase the max JVM heap size (-X
1) make sure the failure was due to an OutOfMemory exception and not
something else.
2) if you have enough memory, increase the max JVM heap size (-Xmx)
3) if you don't need more than 1.5G or so of heap, use the 32 bit JVM
instead (depending on architecture, it can acutally be a little faster
becau
You can also try to clean up index with Luke.
Yonik Seeley wrote:
One possibility: if lucene runs out of memory while adding or optimizing, it
can leave unused files beind that increase the size of the index. A 64 bit
JVM will require more memory than a 32 bit one due to the size of all
referenc
Thank you, Yonik, it seems this is the case.
What can we do in this case? Would running the program with java -d32 be
a solution?
Thanks again,
roxana
One possibility: if lucene runs out of memory while adding or optimizing, it
can leave unused files beind that increase the size of the index.
One possibility: if lucene runs out of memory while adding or optimizing, it
can leave unused files beind that increase the size of the index. A 64 bit
JVM will require more memory than a 32 bit one due to the size of all
references being doubled.
If you are using the compound file format (the def
Hi everybody!
We have a large Lucene index which gets updated very often.
Until recently the java virtual machine used to manage the index was on
32 bits, although the program was running on a 64bits station. Last week
we changed the java to 64 bits and since then we experience strange
problem
