r@lucene.apache.org
>Sent: Friday, May 11, 2012 6:06 AM
>Subject: Re: Suddenly OOM
>
>Outr rambuffer is the default. the Xmx is 75% of the available memory
>on the machine which is 4GB. We've tried increasing it to 85% and even
>gave the machine 10GB of memory. So we more th
-user@lucene.apache.org
>> Cc:
>> Sent: Thursday, May 10, 2012 9:06 AM
>> Subject: Suddenly OOM
>>
>> Hi all,
>>
>> we've been running Solr 1.4 for about a year with no real problems. As
>> of monday it became impossible to do a full import on our mas
/ ElasticSearch / HBase -
http://sematext.com/spm
- Original Message -
> From: Jasper Floor
> To: solr-user@lucene.apache.org
> Cc:
> Sent: Thursday, May 10, 2012 9:06 AM
> Subject: Suddenly OOM
>
> Hi all,
>
> we've been running Solr 1.4 for about
You need to perform Garbage Collection tune up on your JVM to handle the OOM
Sent from my iPhone
On May 10, 2012, at 21:06, "Jasper Floor" wrote:
> Hi all,
>
> we've been running Solr 1.4 for about a year with no real problems. As
> of monday it became impossible to do a full import on our mas
Hi all,
we've been running Solr 1.4 for about a year with no real problems. As
of monday it became impossible to do a full import on our master
because of an OOM. Now what I think is strange is that even after we
more than doubled the available memory there would still always be an
OOM. We seem t
