Hi,
We have an application using Lucene 2.2.0 running in a Sun HotSpot JVM,
with JDK 1.6.0. We have had no problems with it in the 32-bit version of
the JVM. We recently upgraded to 64-bit JVM and occasionally, we are
observing a hang. In particular, the stack trace looks like this - the
Random
RandomAccessFile.readBytes()? In an active system, it would be normal
to see threads blocked there... just on different calls.
If RandomAccessFile.readBytes() is actually hanging, it's not a Lucene
issue, but a JVM/OS bug.
-Yonik
http://www.lucidimagination.com
On Mon, Mar 23, 2009 at 3:31 PM, Venkat R
a few unit tests to confirm its correct
operation.
Is there an interest in pursuing this as a useful capability?
Thanks,
Venkat Rangan
Clearwell Systems Inc.
(650) 526 0639
http://www.clearwellsystems.com <http://www.clearwellsystems.com/>
- Delivering Intelligent eDiscovery
) _ram_8 (1 docs) _ram_9
(1 docs) into _0 (10 docs)
Thanks,
Venkat Rangan
Clearwell Systems Inc.
tioned.
If that's not the case, then it'd be good if you can paste here the
indexing
code including the IndexWriter setup, docs indexing etc.
Shai
On Sun, Jul 26, 2009 at 8:25 AM, Venkat Rangan <
venkat.ran...@clearwellsystems.com> wrote:
> Hi,
>
>
>
> We a
It looks like you're using a version of Lucene before 2.3?
Before 2.3, every document was written to its own RAM segment, and
then these segments were merged during flushing.
Mike
On Sun, Jul 26, 2009 at 2:42 AM, Venkat
Rangan wrote:
> Shai,
>
> Thanks for your response. T
