RE: MappedByteBuffer duplicates

2017-02-27 Thread Uwe Schindler
sing Solr or Elasticsearch on multiple machines). The bad thing on Windows is: You cannot use another IO system: - NIOFSDirectory is too slow (Windows bug with multithreaded access) - on Linux one may use NIOFSDirectory instead of MMapDirectory if you run out of virtual address space - SimpleFSDirector

RE: MappedByteBuffer duplicates

2017-02-27 Thread Kameron Cole
t any discussion of ulimits is moot, right? From: "Uwe Schindler" To: Date: 02/24/2017 06:22 PM Subject:RE: MappedByteBuffer duplicates Hi, You did not give us all information. So I can only give some hints, because there could be multiple causes for your probl

RE: MappedByteBuffer duplicates

2017-02-24 Thread Uwe Schindler
e > From: "Uwe Schindler" > To: > Date: 02/24/2017 01:39 PM > Subject:RE: MappedByteBuffer duplicates > > > > Hi, > > that is not an issue, the duplicates are required for so called IndexInput > clones and splices. Every search request

Re: MappedByteBuffer duplicates

2017-02-24 Thread Greg Bowyer
e > MappedByteBuffer > objects are being retained. > > > > > > From: "Uwe Schindler" > To: > Date: 02/24/2017 01:39 PM > Subject:RE: MappedByteBuffer duplicates > > > > Hi, > > that is not an issue, the duplicates are required for

RE: MappedByteBuffer duplicates

2017-02-24 Thread Kameron Cole
eBuffer objects are being retained. From: "Uwe Schindler" To: Date: 02/24/2017 01:39 PM Subject:RE: MappedByteBuffer duplicates Hi, that is not an issue, the duplicates are required for so called IndexInput clones and splices. Every search request will create

RE: MappedByteBuffer duplicates

2017-02-24 Thread Uwe Schindler
Hi, that is not an issue, the duplicates are required for so called IndexInput clones and splices. Every search request will create many of them. But there is no need to worry, they are just thin wrappers - they don't allocate any extra off-heap memory. They are just there to have a separate po