ok i opened https://issues.apache.org/jira/browse/LUCENE-2832
On Fri, Dec 24, 2010 at 12:44 PM, Robert Muir wrote:
> On Fri, Dec 24, 2010 at 12:28 PM, Yonik Seeley
> wrote:
>> On Fri, Dec 24, 2010 at 10:23 AM, Robert Muir wrote:
>>> hmm, i think you are actually running out of virtual address s
On Fri, Dec 24, 2010 at 12:28 PM, Yonik Seeley
wrote:
> On Fri, Dec 24, 2010 at 10:23 AM, Robert Muir wrote:
>> hmm, i think you are actually running out of virtual address space,
>> even on 64-bit!
>
> I don't know if there are any x86 processors that allow 64 bits of
> address space yet.
> AFAI
On Fri, Dec 24, 2010 at 10:23 AM, Robert Muir wrote:
> hmm, i think you are actually running out of virtual address space,
> even on 64-bit!
I don't know if there are any x86 processors that allow 64 bits of
address space yet.
AFAIK, they are mostly 48 bit.
> http://msdn.microsoft.com/en-us/libr
hmm, i think you are actually running out of virtual address space,
even on 64-bit!
http://msdn.microsoft.com/en-us/library/aa366778(v=VS.85).aspx#memory_limits
Apparently windows limits you to 8TB virtual address space
(ridiculous), so i think you should try one of the following:
* continue usin
At root, it's an OOM:
Caused by: java.lang.OutOfMemoryError: Map failed at
I'm guessing that you're optimizing after the import? What are the
JVM settings you're using? The standard response is "increase
the amount of memory available to the JVM", but it's expensive
to change it and only find out
Hi all,
I have created a new index (using Solr trunk version from 17th December,
running on Windows 7 & Tomcat 6, 64 bit JVM) with around 1.1 billion of
documents (index size around 550GB, mergeFactor=20).
After the (csv) import I have commited the data and got this error:
HTTP Status 500 - Seve
