Hi, thanks for the links and for your help. The server is now running third day in a row with no issues. What is done: 1. Applied these GC tuning options: -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=80 2. Optimized the schema and index size (decreased at least 8 times). 3. Updated the application code. Previously we've indexed lots of data that we shouldn't, lots of html content which is now removed from data before indexing. In combination with NGramFilterFactory with gram size 1..20 all this constituted an explosive mixture. This caused high load during indexing and result to a big redundant index.
But my previous thought about stability is still valid. I observed that when shard goes down (both shard all its replicas were down) caused some docs to be missing from the index. So in case when shards are on separate physical servers and one of the servers will go down (by any reason) could cause troubles. Best, Alex -- View this message in context: http://lucene.472066.n3.nabble.com/ColrCloud-IOException-occured-when-talking-to-server-at-tp4061831p4063161.html Sent from the Solr - User mailing list archive at Nabble.com.
