Hmmm, may we see your solrconfig.xml file? You're right, this is a relatively vanilla test and should be just fine. BTW, I don't know what your latency requirements are, but extending your auto soft commit interval to as long as you can stand isn't a bad idea. the soft commit will invalidate a number of top-level caches, and add to the load so it's best to have that be longer.
Do note that solr cloud doesn't use replication the same way it used to, so the fact that your *:* queries are giving inconsistent results is _very_ suspicious, almost as though you are mixing old replication in there somehow. Does this happen only when you're actively indexing? in other words do you go from consistent->inconsistent states? Best Erick On Fri, May 31, 2013 at 4:46 PM, ltenny <lte...@gmail.com> wrote: > Wonderful discussion, but it seems that the exact values here should only > affect the freshness of the search results and the growth of the logs. What > I have going on in a very simple, 10 node SolrCloud with quite low insert > rates (10K docs/20 minutes) absolutely kills the cloud in the first 20 > minutes. All the nodes spew out the EofException, searches provide > inconsistent results, and the whole thing deteriorates into a bowl of mush. > This is a simple and small use case...I really must have something wildly > misconfigurated. > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Getting-tons-of-EofException-with-jetty-SolrCloud-tp4067427p4067457.html > Sent from the Solr - User mailing list archive at Nabble.com.
