lt merge policy settings, we get the same results.
> >>>
> >>>
> >>>
> >>> We have not tried to dump the table to a comma separated file. We
> think
> >>> that dumping this size table to disk will introduce other memory
> problems
> >&
mp the table to a comma separated file. We
> think
> >>> that dumping this size table to disk will introduce other memory
> problems
> >>> with big file management. We have not tested that case.
> >>>
> >>>
> >>> On Fri, Apr 4
t;>>> What happens when you use default merge policy settings?
>>>>
>>>> What happens when you dump your table to Comma Separated File and fed
>>>> that file to solr?
>>>>
>>>> Ahmet
>>>>
>>>> On Friday, April 4, 2014 5:10
;
>>> >>> />
>>> >>> name="ADDRESS_ACCT_ALL.ADDR_NAME_abc" />
>>> >
>>> >
>>> >>> name="ADDRESS_ACCT_ALL.EMAIL_ADDR_abc"
>>> >/>
>>> >
>>> >
>>>
not tried to dump the table to a comma separated file. We
>> think
>> >> that dumping this size table to disk will introduce other memory
>> problems
>> >> with big file management. We have not tested that case.
>> >>
>> >>
>> >> On Fri
>> Which database are you using? Can you send us data-config.xml?
>> >>
>> >> What happens when you use default merge policy settings?
>> >>
>> >> What happens when you dump your table to Comma Separated File and fed
>> >> th
gt; wrote:
>>>
>>> The ramBufferSizeMB was set to 6MB only on the test system to make the
>>> system crash sooner. In production that tag is commented out which
>>> I believe forces the default value to be used.
>>>
>>>
>>>
&
gt; >>
>> >> What happens when you use default merge policy settings?
>> >>
>> >> What happens when you dump your table to Comma Separated File and fed
>> >> that file to solr?
>> >>
>> >> Ahmet
&g
t; >> candygram.for.mo...@gmail.com> wrote:
> >>
> >> The ramBufferSizeMB was set to 6MB only on the test system to make the
> >> system crash sooner. In production that tag is commented out which
> >> I believe forces the default value to be u
gt;> >out of curiosity, why did you set ramBufferSizeMB to 6?
>> >
>> >Ahmet
>> >
>> >
>> >
>> >
>> >
>> >On Friday, April 4, 2014 3:27 AM, Candygram For Mongo <
>> candygram.for.mo...@gmail.com> wrote:
>>
to be used.
>>
>>
>>
>>
>> On Thu, Apr 3, 2014 at 5:46 PM, Ahmet Arslan wrote:
>>
>> Hi,
>> >
>> >out of curiosity, why did you set ramBufferSizeMB to 6?
>> >
>> >Ahmet
>> >
>> >
>> >
>>
M, Ahmet Arslan wrote:
>
> Hi,
> >
> >out of curiosity, why did you set ramBufferSizeMB to 6?
> >
> >Ahmet
> >
> >
> >
> >
> >
> >On Friday, April 4, 2014 3:27 AM, Candygram For Mongo <
> candygram.for.mo...@gmail.com> wrote:
> &
B to 6?
>
>Ahmet
>
>
>
>
>
>On Friday, April 4, 2014 3:27 AM, Candygram For Mongo
> wrote:
>*Main issue: Full Indexing is Causing a Java Heap Out of Memory Exception
>
>*SOLR/Lucene version: *4.2.1*
>
>
>*JVM version:
>
>Java(TM) SE Runtime En
d you set ramBufferSizeMB to 6?
>
> Ahmet
>
>
>
>
> On Friday, April 4, 2014 3:27 AM, Candygram For Mongo <
> candygram.for.mo...@gmail.com> wrote:
> *Main issue: Full Indexing is Causing a Java Heap Out of Memory Exception
>
> *SOLR/Lucene version: *4.2.1*
>
> *J
Hi,
out of curiosity, why did you set ramBufferSizeMB to 6?
Ahmet
On Friday, April 4, 2014 3:27 AM, Candygram For Mongo
wrote:
*Main issue: Full Indexing is Causing a Java Heap Out of Memory Exception
*SOLR/Lucene version: *4.2.1*
*JVM version:
Java(TM) SE Runtime Environment (build
*Main issue: Full Indexing is Causing a Java Heap Out of Memory Exception
*SOLR/Lucene version: *4.2.1*
*JVM version:
Java(TM) SE Runtime Environment (build 1.7.0_07-b11)
Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode)
*Indexer startup command:
set JVMARGS=-XX:MaxPermSize
16 matches
Mail list logo
