On 3/6/2014 3:37 PM, Martin de Vries wrote: > We have 5 Solr servers in a Cloud with about 70 cores and 12GB > indexes in total (every core has 2 shards, so it's 6 GB per server). > > After upgrade to Solr 4.7 the Solr servers are crashing constantly > (each server about one time per hour). We currently don't have any clue > about the reason. We tried loads of different settings, but nothing > works out. > > When a server crashes the last log item is (most times) a > "Broken pipe" error. The last queries / used cores are completely random > (as far as we can see).
We'd need to actually see a large chunk of the end of the actual logfile. It must be the file, not the logging tab in the admin UI. Ideally it should be at the INFO logging level. If the broken pipe error is part of an EofException, it is (in my experience) caused by a client disconnecting before sending the full request or disconnecting before Solr responds. I don't know what kind of socket timeout your clients have, but 30-60 seconds is a common default for systems that actually set a timeout. Are there any messages in the operating system logs? Full details about the computer, operating system, Solr startup options, and your index may also be required to dig deeper, so any details you can share will be useful. The config and schema may also be useful, but you can hold off on those until we know for sure whether they will be needed. Thanks, Shawn
