Hi,
We are in the process of upgrading from lucene 3.6.0 to lucene 4.7.2,
and our tests show a significant search degradation on Windows platform.
Trying to figure this out, here are a couple of points we noticed.
Any suggestions/thoughts will be greatly appreciated.
Thanks!
1) Running sea
Hi all,
Using lucene 3.6.2, we are trying to search a pretty small collection.
To open the directory we use Mmap since we are running on a 64 bit linux
machine, and we usually get much better results than using SimpleFS or
NIO.
Although the collection is only a few GB in size, we are getting
gt;
> http://stackoverflow.com/questions/8892143/error-when-opening-a-
> lucene-index-map-failed
>
> Harald.
>
> On 18.08.2014 13:10, Shlomit Rosen wrote:
> > Hi all,
> >
> > Using lucene 3.6.2, we are trying to search a pretty small collection.
> > To open the
Hello :)
We have a customer who's system keeps crashing at certain queries.
At default we use Mmap directory for search as it usually gives us the
best performance.
Although the heap usage seemed normal, we asked them to switch to
NIOFSDirectory to make sure it's not a memory issue...
The sys
Hello,
We are using lucene 3.6.0.
We ran optimize on a large collection (250 GB before optimization), during
which we ran out of disk space.
After adding more disk space, we re-ran the optimization, and the process
completed successfully.
However, the index size didn't change very much, and l
Hello,
We have a client that is using lucene 3.0.3.
They are working with NAS storage device which recently had permission
issues,
which might have generated some "out of disk space" exceptions during
indexing.
We are uncertain if they also suffered JDK crashes in the past few months,
as we
Hello,
We have a client that is using lucene 3.0.3.
They are working with NAS storage device which recently had permission
issues,
which might have generated some "out of disk space" exceptions during
indexing.
We are uncertain if they also suffered JDK crashes in the past few months,
as we
