On Mon, Feb 22, 2010 at 6:39 PM, Jay Hill wrote:
> It's just that, in a
> running system, it's probably very rare that there is only a single segment
> for any meaningful length of time.
Right - but the performance impact of a huge merge can be non-trivial.
People wishing to avoid the biggest of
Thanks for clearing that up guys, I misspoke slightly. It's just that, in a
running system, it's probably very rare that there is only a single segment
for any meaningful length of time. Unless that merge-down-to-one occurs
right when indexing stops there will almost always be a new (small) segment
Also, a mergefactor of 1 is actually invalid - 2 is the lowest you can go.
--
- Mark
http://www.lucidimagination.com
On Sun, Feb 21, 2010 at 2:20 PM, David Smiley @MITRE.org
wrote:
> I've always thought that these two events were effectively equivalent. --
> the results of an optimize vs the results of Lucene _naturally_ merging all
> segments together into one.
Correct. Occasionally one hit's a "major" merge
merge down to.
>
> -Jay
> ...
>
--
View this message in context:
http://old.nabble.com/optimize-is-taking-too-much-time-tp27561570p27693177.html
Sent from the Solr - User mailing list archive at Nabble.com.
-
> > Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> > Hadoop ecosystem search :: http://search-hadoop.com/
> >
> >
> >
> > - Original Message
> >> From: mklprasad
> >> To: solr-user@lucene.apache.org
> >> Sent: Fri, February
; From: mklprasad
>> To: solr-user@lucene.apache.org
>> Sent: Fri, February 19, 2010 1:02:11 AM
>> Subject: Re: optimize is taking too much time
>>
>>
>>
>>
>> Jagdish Vasani-2 wrote:
>> >
>> > Hi,
>> >
>> > y
2:11 AM
> Subject: Re: optimize is taking too much time
>
>
>
>
> Jagdish Vasani-2 wrote:
> >
> > Hi,
> >
> > you should not optimize index after each insert of document.insted you
> > should optimize it after inserting some good no of documents.
emory and time
>>
>>
>> can any body please tell do we have any property in solr to get rid of
>> this.
>>
>> Thanks in advance
>>
>> --
>> View this message in context:
>> http://old.nabble.com/optimize-is-taking-too-much-time-tp2756157
,
From: Jagdish Vasani
To: solr-user@lucene.apache.org
Sent: Thu, February 18, 2010 3:12:15 PM
Subject: Re: optimize is taking too much time
Hi,
you should not optimize index after each insert of document.insted you
should optimize it after inserting some good no
; Thanks in advance
>
> --
> View this message in context:
> http://old.nabble.com/optimize-is-taking-too-much-time-tp27561570p27561570.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
>
to call in that case for my 50Gb will it takes less time .
>
>
> Please clearify me
> Thanks in advance
>
>
>
>
--
View this message in context:
http://old.nabble.com/optimize-is-taking-too-much-time-tp27561570p27634994.html
Sent from the Solr - User mailing list archive at Nabble.com.
: in my solr u have 1,42,45,223 records having some 50GB .
: Now when iam loading a new record and when its trying optimize the docs its
: taking 2 much memory and time
: can any body please tell do we have any property in solr to get rid of this.
Solr isn't going to optimize the index unless y
context:
http://old.nabble.com/optimize-is-taking-too-much-time-tp27561570p27561570.html
Sent from the Solr - User mailing list archive at Nabble.com.
14 matches
Mail list logo