I am using Solr 5.3.1 and we are facing OutOfMemory exception while doing some complex wildcard and proximity query (even for simple wildcard query). We are doing distributed solr search using shard across 20 cores.
The problem description is given below. For example simple query like *q=Tile:(eleme* OR proces*)&timeAllowed=50* It gives warning given below *2016-01-08 14:14:03,874 WARN org.apache.solr.search.SolrIndexSearcher – Query: Tile:(eleme* OR proces*); The request took too long to iterate over terms. Timeout: timeoutAt: 5804340135470 (System.nanoTime(): 5804342454166), TermsEnum=org.apache.lucene.codecs.blocktree.IntersectTermsEnum@1d2d4fb* I don't understand why the timeout thrown by SolrIndexSearcher is showing 5804340135470 nanosecond (5804.342454166001 seconds), even I already given timeout of 1000 ms (1 second). Is the log message is correct ? Help me to understand this problem. -- View this message in context: http://lucene.472066.n3.nabble.com/SolrIndexSearcher-throws-Misleading-Error-Message-When-timeAllowed-is-Specified-tp4249356.html Sent from the Lucene - Java Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
