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
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 that come in
large bursts. My server
On Mon, Sep 15, 2008 at 2:17 PM, Paleo Tek [EMAIL PROTECTED] wrote:
1) I can't find anything intersterting in the container logs.
Is the client timing out the connection?
If Solr were encountering errors, they would be logged.
-Yonik
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
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 that come in
large bursts. My server is a multiprocessor with plenty of memory, so I
can multi-thread
On Fri, Sep 12, 2008 at 11:19 AM, Paleo Tek [EMAIL PROTECTED] wrote:
Using jetty, there is ~10% failure rate with no server response code
received.
What happened then? Did the network connection just drop, or did the
server or client time it out? How can you tell it failed?
-Yonik
