Hi, thanks for the response. Seems like this is the case because there are no any other applications that could fire commit/optimize calls. All commits are triggered by Solr and the optimize is triggered by a cron task.
Because of all that it looks like a bug in Solr. It probably should not run commits when optimize is in the process or should do commit before the optimize. Or should not run optimize when a commit is in the process. Not sure which exactly scenario happens. Is there anything I can do to fix this? I don't have too much memory on this server and since this could lead to double the RAM used it is a serious issue for me. Best, Alex -- View this message in context: http://lucene.472066.n3.nabble.com/Overlapping-onDeckSearchers-2-tp772556p4066205.html Sent from the Solr - User mailing list archive at Nabble.com.
