I added what I considered a first draft into the solrconfig.xml wiki.
Bill
On 6/23/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: You can put a load balancer in front of the pool of slave servers for
that.
Solr does have some features designed to make Load Balancing easy
* "healthcheck"
On Jun 24, 2006, at 4:29 PM, Yonik Seeley wrote:
On 6/24/06, Erik Hatcher <[EMAIL PROTECTED]> wrote:
This weekend :) I have imported more data than my hacked
implementation can handle without bumping up Jetty's JVM heap size,
so I'm now at the point where it is necessary for me to start using
I'm trying to fully understand the LRUCache and the autowarmCount
parameter. Why does it make sense to auto-warm filters and query
results? In my case, if a new document is added it may invalidate
many filters, and it would require knowing the details of the
documents added/removed to k
: I'm trying to fully understand the LRUCache and the autowarmCount
: parameter. Why does it make sense to auto-warm filters and query
: results? In my case, if a new document is added it may invalidate
: many filters, and it would require knowing the details of the
: documents added/removed t
That's great information, thanks Bill
On 6/26/06, Bill Au <[EMAIL PROTECTED]> wrote:
I added what I considered a first draft into the solrconfig.xml wiki.
Bill
On 6/23/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
>
>
> : You can put a load balancer in front of the pool of slave servers for
: It may not even be necessary to cache this type of lookup since it is
: simply a TermEnum through specific fields in the index. Maybe simply
: doing the TermEnum in the request handler instead of iterating
: through a cache would be just as fast or faster. Any thoughts on that?
While commutin
