Okay, thanks for the suggestion, will try to decrease the caches gradually. Each node has near 50 000 000 docs, perhaps we need more shards...
We had smaller caches before but that was leading to bad feedback from our users. Besides our application users we also use Solr internally for data analyze (very basic, simple searches for lists of keywords to determine docs category, but we run a lot of such queries). Previously it was possible to point those internal queries to one node (replica) and queries received from the users to another, so the caches did not interfere with each other. Not sure how to do this now with SolrCloud, it seems doesn't matter to which node we send requests, SolrCloud decides which nodes will process it. Am I wrong? Best, Alex -- View this message in context: http://lucene.472066.n3.nabble.com/Endless-100-CPU-usage-on-searcherExecutor-thread-tp4175088p4175285.html Sent from the Solr - User mailing list archive at Nabble.com.
