Marcus wrote:
> --bcaec53043296dfbfd04a0ece1ac
> Content-Type: text/plain; charset=ISO-8859-1
>
> we're currently using 4GB max heap.
> We recently moved from 2GB to 4GB when we discovered it prevented a crash
> with a certain set of docs.
> Marcus
I've tried the same workaround with the heap i
we're currently using 4GB max heap.
We recently moved from 2GB to 4GB when we discovered it prevented a crash
with a certain set of docs.
Marcus
On Thu, Apr 14, 2011 at 5:01 PM, Andi Vajda wrote:
>
> On Thu, 14 Apr 2011, Marcus wrote:
>
> thanks.
>>
>> I have documents that will consistently ca
On Thu, 14 Apr 2011, Marcus wrote:
thanks.
I have documents that will consistently cause this upon writing them to the
index. let me see if I can reduce them down to the crux of the crash.
granted, these are docs are very large, unruly "bad" data, that should have
never gotten this stage in ou
thanks.
I have documents that will consistently cause this upon writing them to the
index. let me see if I can reduce them down to the crux of the crash.
granted, these are docs are very large, unruly "bad" data, that should have
never gotten this stage in our pipeline, but I was hoping for a java
On Thu, 14 Apr 2011, Marcus wrote:
in certain cases when a java/pylucene exception occurs, it gets passed up
in my code, and I'm able to analyze the situation.
sometimes though, the python process just crashes, and if I happen to be in
top (linux top that is), I see a JCC exception flash up i
