You have a large index with tough performance requirements on one server.
I would analyze your system to see if it's got any bottlenecks.
Watch out for auto-warming taking too long so it does not finish before next
commit()
Watch out for too frequent commits
Monitor mem usage (JConsole or similar)
i am using NRT, and the caches are not always warmed, i think this is almost
a problem !?
-
--- System
One Server, 12 GB RAM, 2 Solr Instances, 7 Cores,
1 Core with 31 Million Documents other Cores < 100.000
- Solr1 for Se
Are you using shards or have everything in same index?
- shards == distributed Search over several cores ? => yes, but not always.
but in generally not.
What problem did you experience with the StatsCompnent?
- if i use stats on my 34Million Index, no matter how many docs founded, the
sum takes V
Are you using shards or have everything in same index?
What problem did you experience with the StatsCompnent? How did you use it? I
think the right approach will be to optimize StatsComponent to do quick sum()
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
On 8. mar
