On Mon, Jun 7, 2010 at 10:35 AM, <[email protected]> wrote: > Hi folks, > > This morning I was experimenting with using multiple threads while indexing > some 20,000,000 records worth of content. In fact, my test spun up some 50 > threads, and happily chugged away for a couple of hours before I saw the > following output from my test code: > >>>>>>> > Http protocol error: HTTP/1.1 400 missing_content_stream, while trying to > index record 6469124 > Http protocol error: HTTP/1.1 400 missing_content_stream, while trying to > index record 6469551 > Http protocol error: HTTP/1.1 400 missing_content_stream, while trying to > index record 6470592 > Http protocol error: HTTP/1.1 400 missing_content_stream, while trying to > index record 6472454 > java.net.SocketException: Connection reset > at java.net.SocketInputStream.read(SocketInputStream.java:168) > at HttpPoster.getResponse(HttpPoster.java:280) > at HttpPoster.indexPost(HttpPoster.java:191) > at ParseAndLoad$PostThread.run(ParseAndLoad.java:638) > <<<<<< [...] > It is unlikely (but, of course, not out of the question) that this hiccup is > due to some reentrancy problem in my test code. It is much more likely to > be some kind of a Solr multi-threaded race condition – especially since it > looks like a number of requests all failed at precisely the same time.
Interesting. The exception messages suggest it would be an issue with parsing/getting content streams. How are you sending the documents? Multi-part POST? That would go through MultipartRequestParser and commons ServletFileUpload to parse that. -Yonik http://www.lucidimagination.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
