How is DeletionPolicy supposed to work?

Hi folks, In moving to 1.4, it was unclear to me how deletionPolicy was supposed to work. I commit/optimize on a build server, then replicate to multiple search servers. I don't need anything fancy for a deletion policy: save one copy, and replicate on copy. But when I used no policy, so

Re: No server response code on insert: how do I avoid this at high speed?

Otis Gospodnetic wrote: Perhaps the container logs explain what happened? How about just throttling to the point where the failure rate is 0%? Too slow? Otis's questions regarding dropped inserts sent me back to the drawing board. The system had been tuned to a slower database to optimiz

Re: No server response code on insert: how do I avoid this at high speed?

Solr - Nutch - Original Message From: Paleo Tek <[EMAIL PROTECTED]> To: solr-user@lucene.apache.org Sent: Friday, September 12, 2008 11:19:52 AM Subject: No server response code on insert: how do I avoid this at high speed? I have a largish index with a lot of churn, and inserts

No server response code on insert: how do I avoid this at high speed?

I have a largish index with a lot of churn, and inserts that come in large bursts. My server is a multiprocessor with plenty of memory, so I can multi-thread and stuff in about 1.6 million records per hour, going full speed. I use a dozen or so threads to post curl inserts, and monitor the re