Hoping that others will chime in here with other ideas. Have you, though, tried reducing the JVM memory, leaving more available for the OS disk cache? Having said that, I'd expect that to improve performance, not to cause JVM crashes.
It might also help to know what version of Java you are running. Upayavira On Mon, Aug 17, 2015, at 12:45 PM, Modassar Ather wrote: > The servers have 32g memory each. Solr JVM memory is set to -Xms20g > -Xmx24g. There are no OOM in logs. > > Regards, > Modassar > > On Mon, Aug 17, 2015 at 5:06 PM, Upayavira <u...@odoko.co.uk> wrote: > > > How much memory does each server have? How much of that memory is > > assigned to the JVM? Is anything reported in the logs (e.g. > > OutOfMemoryError)? > > > > On Mon, Aug 17, 2015, at 12:29 PM, Modassar Ather wrote: > > > Hi, > > > > > > I have a Solr cluster which hosts around 200 GB of index on each node and > > > are 6 nodes. Solr version is 5.2.1. > > > When a huge query is fired, it times out *(The request took too long to > > > iterate over terms.)*, which I can see in the log but at same time the > > > one > > > of the Solr node goes down and the logs on the Solr nodes starts showing > > > > > > > > > *following exception.org.apache.solr.common.SolrException: no servers > > > hosting shard.* > > > For sometime the shards are not responsive and other queries are not > > > searched till the node(s) are back again. This is fine but what could be > > > the possible cause of solr node going down. > > > The other exception after the solr node goes down is leader election > > > related which is not a concern as there is no replica of the nodes. > > > > > > Please provide your suggestions. > > > > > > Thanks, > > > Modassar > >
