Hello,
we are experiencing OOM exceptions in our single core solr instance
(on a (huge) amazon EC2 machine).
We investigated a lot in the mailing list and through jmap/jhat dump
analyzing and the problem resides in the lucene FieldCache that fills
the heap and blows up the server.
Our index is qui
lso facet values for a field) should be
> controlled by a fixed-size cache, but they are not.
>
> On Fri, Jun 18, 2010 at 7:52 AM, Matteo Fiandesio
> wrote:
>> Hello,
>> we are experiencing OOM exceptions in our single core solr instance
>> (on a (huge) amazon EC2
larger EC2 instances.
>
> On Mon, Jun 21, 2010 at 2:08 AM, Matteo Fiandesio
> wrote:
>> Compiling solr with lucene 2.9.3 instead of 2.9.1 will solve this issue?
>> Regards,
>> Matteo
>>
>> On 19 June 2010 02:28, Lance Norskog wrote:
>>> The Lucene
your index frequently and re-opening readers often?
> If so, how?
>
> I'm assuming that if you do NOT sort on all these fields, you don't have
> the problem, is that true?
>
> Best
> Erick
>
> On Fri, Jun 18, 2010 at 10:52 AM, Matteo Fiandesio <
> matteo.fi
tely by firing off enough sort queries at the server. It'll
> tell you a lot if you can't make this happen, even on a relatively small
> test machine.
>
> Best
> Erick
>
> On Tue, Jun 22, 2010 at 12:59 PM, Matteo Fiandesio <
> matteo.fiande...@gmail.com> wrote
gards,
Matteo
On 22 June 2010 22:41, Matteo Fiandesio wrote:
> Fields over i'm sorting to are dynamic so one query sorts on
> erick_time_1,erick_timeA_1 and other sorts on erick_time_2 and so
> on.What we see in the heap are a lot of arrays,most of them,filled
> with 0s maybe due
