it in steps (max segments parameter)
>>
>> 10 -> 9 -> 8 -> 7 .. -> 1
>>
>> that way less segments need to be merged in one go.
>>
>> testing your index will show you what a good maximum
>> amount of segments is for your index.
>>
>>>
Thanks @Erick for the suggestions. That looks so bad, yes your assumptions
are right, we have lot of delete & index documents as well.
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Thanks Shawn for suggestions. Interesting to know deleteByQuery has some
impact, will try to change it as you have suggested. Thabks
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Thanks @Nicolas Franck for reply, i don't see any any segment info for 4.4
version. Is there any API i can use to get my segment information ? Will try
to use maxSegments and see if it can help us during optimization.
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Hello guys,
We have 4 solr(version 4.4) instance on production environment, which are
linked/associated with zookeeper for replication. We do heavy deleted & add
operations. We have around 26million records and the index size is around
70GB. We serve 100k+ requests per day.
Because of heavy
I configured filter cache in solrconfig.xml as here under :
filterCache
class=solr.FastLRUCache
size=16384
initialSize=4096
autowarmCount=4096/
useFilterForSortedQuerytrue/useFilterForSortedQuery
as per
http://wiki.apache.org/solr/SolrCaching#head-b6a7d51521d55fa0c89f2b576b2659f297f9
And
.
On Tue, Sep 22, 2009 at 8:46 PM, Yonik Seeley yo...@lucidimagination.comwrote:
Solr's caches should be transparent - they should only speed up
queries, not change the result of queries.
-Yonik
http://www.lucidimagination.com
On Tue, Sep 22, 2009 at 9:45 AM, satyasundar jena tosatyaj
