> most of the Solr sites I know of
> have much larger indexes than ram and expect everything to work
> smoothly
Hmm... In that case, throttling the merges would probably help most,
though, yes, that's not available today. In lieu of that, I'd run
large merges during off-peak hours, or better yet,
Ok. I was talking about what tools are available now- much better
things are in the NRT work. I don't know how merges work now, in re
multitasking and thread contention. Most of the Solr sites I know of
have much larger indexes than ram and expect everything to work
smoothly.
Lance
On Sun, Jan 9,
> The older MergePolicies followed a strategy which is quite disruptive in an
> NRT environment.
Can you elaborate as to why (maybe we need to place this in a wiki)?
If large merges are running in their own thread, they should not
disrupt queries, eg, there won't be CPU contention. The IO conten
Thanks Lance for mentioning the MergePolicies and specifically this one
contributed by LinkedIn.
2011/1/8 Lance Norskog
> There are always slowdowns when merging new segments during indexing.
> A MergePolicy decides when to merge segments. The older MergePolicies
> followed a strategy which is
There are always slowdowns when merging new segments during indexing.
A MergePolicy decides when to merge segments. The older MergePolicies
followed a strategy which is quite disruptive in an NRT environment.
There is a new feature in 3.x & the trunk called
'BalancedSegmentMergePolicy'. This new
Thanks Yonik,
Using a stable release of Solr what would you suggest to do - given
MultiSearch's demise and the other work is still ongoing?
2011/1/6 Yonik Seeley
> On Thu, Jan 6, 2011 at 12:37 PM, Stephen Boesch wrote:
> > Solr/lucene newbie here ..
> >
> > We would like searches against a so
On Thu, Jan 6, 2011 at 12:37 PM, Stephen Boesch wrote:
> Solr/lucene newbie here ..
>
> We would like searches against a solr/lucene index to immediately be able to
> view data that was added. I stress "small" amount of new data given that
> any significant amount would require excessive latency
Solr/lucene newbie here ..
We would like searches against a solr/lucene index to immediately be able to
view data that was added. I stress "small" amount of new data given that
any significant amount would require excessive latency.
Looking around, i'm wondering if the direction would be a Mult
