Hi Yonik,

Thanks for your reply.

I tried increasing the maxClauseCount to a bigger value. But what could be the 
ideal value and will not that hit the performance? What are the chances that if 
we increase the value we will not face this issue again?

As you asked pasting below the full trace of the error

Problem accessing /solr/ar/select/. Reason:
    maxClauseCount is set to 1024

org.apache.lucene.search.BooleanQuery$TooManyClauses: maxClauseCount is set to 
1024
        at org.apache.lucene.search.BooleanQuery.add(BooleanQuery.java:136)
        at org.apache.lucene.search.BooleanQuery.add(BooleanQuery.java:127)
        at 
org.apache.lucene.search.ScoringRewrite$1.addClause(ScoringRewrite.java:51)
        at 
org.apache.lucene.search.ScoringRewrite$1.addClause(ScoringRewrite.java:55)
        at 
org.apache.lucene.search.ScoringRewrite$3.collect(ScoringRewrite.java:95)
        at 
org.apache.lucene.search.TermCollectingRewrite.collectTerms(TermCollectingRewrite.java:38)
        at 
org.apache.lucene.search.ScoringRewrite.rewrite(ScoringRewrite.java:93)
        at 
org.apache.lucene.search.MultiTermQuery.rewrite(MultiTermQuery.java:312)
        at 
org.apache.lucene.search.highlight.WeightedSpanTermExtractor.extract(WeightedSpanTermExtractor.java:158)
        at 
org.apache.lucene.search.highlight.WeightedSpanTermExtractor.extract(WeightedSpanTermExtractor.java:98)
        at 
org.apache.lucene.search.highlight.WeightedSpanTermExtractor.getWeightedSpanTerms(WeightedSpanTermExtractor.java:391)
        at 
org.apache.lucene.search.highlight.QueryScorer.initExtractor(QueryScorer.java:216)
        at 
org.apache.lucene.search.highlight.QueryScorer.init(QueryScorer.java:185)
        at 
org.apache.lucene.search.highlight.Highlighter.getBestTextFragments(Highlighter.java:205)
        at 
org.apache.solr.highlight.DefaultSolrHighlighter.doHighlightingByHighlighter(DefaultSolrHighlighter.java:490)
        at 
org.apache.solr.highlight.DefaultSolrHighlighter.doHighlighting(DefaultSolrHighlighter.java:401)
        at 
org.apache.solr.handler.component.HighlightComponent.process(HighlightComponent.java:131)
        at 
org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:186)
        at 
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:129)
        at org.apache.solr.core.SolrCore.execute(SolrCore.java:1376)
        at 
org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:365)
        at 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:260)
        at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
        at 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
        at 
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
        at 
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
        at 
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
        at 
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
        at 
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
        at 
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
        at org.mortbay.jetty.Server.handle(Server.java:326)
        at 
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
        at 
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
        at 
org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
        at 
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

Regards,
Sawan

From: Yonik Seeley-4 [via Lucene] 
[mailto:ml-node+s472066n4056967...@n3.nabble.com]
Sent: Thursday, April 18, 2013 5:09 PM
To: Sawan Verma
Subject: Re: TooManyClauses: maxClauseCount is set to 1024

Can you provide a full stack trace of the exception?

There's a maxClauseCount in solrconfig.xml that you can increase to
work around the issue.

-Yonik
http://lucidworks.com


On Thu, Apr 18, 2013 at 7:31 AM, sawanverma <[hidden 
email]</user/SendEmail.jtp?type=node&node=4056967&i=0>> wrote:

> Its quite confusing about this error.
>
> I had a situation where i have to turn on the highlighting. In some cases
> though the number of docs found for a particular query was for example say
> 2, the highlighting was coming only for 1. I did some checks and found that
> that particular text searched was in the bigger document and was towards the
> end of the document.
>
> So i increased the hl.maxAnalyzedChar from default value of 51200 to a
> bigger value say 5000000. And then it started working, i mean now the
> highlighting was working properly.
>
> Now, i have encountered one more problem with the same error.
>
> There is a document which is returning the maxClauseCount error when i do
> search on content:*. The document is quite big big in size and the
> hl.maxAnalyzedChars was default i.e. 51200.
>
> I tried decreasing that i found that the error is coming exactly at 31375
> char (this is did my setting the hl.maxAnalyzedChars to 31375. it worked
> fine till 31374).
>
> Solutions are most welcome as i am in great need of this.
>
> Sample query is as below
> http://localhost:8983/solr/test/select/?q=content:* AND
> obs_date:[2010-01-01T00:00:00Z%20TO%202011-12-31T23:59:59Z]&fl=content&hl=true&hl.fl=content&hl.snippets=1&hl.fragsize=1500&hl.requireFieldMatch=true&hl.alternateField=content&hl.maxAlternateFieldLength=1500&hl.maxAnalyzedChars=31375&facet.limit=200&facet.mincount=1&start=64&rows=1&sort=obs_date%20desc
>
> Regards,
> Sawan
>
>
>
> --
> View this message in context: 
> http://lucene.472066.n3.nabble.com/TooManyClauses-maxClauseCount-is-set-to-1024-tp4056965.html
> Sent from the Solr - User mailing list archive at Nabble.com.

________________________________
If you reply to this email, your message will be added to the discussion below:
http://lucene.472066.n3.nabble.com/TooManyClauses-maxClauseCount-is-set-to-1024-tp4056965p4056967.html
To unsubscribe from TooManyClauses: maxClauseCount is set to 1024, click 
here<http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4056965&code=c2F3YW4udmVybWFAZ2xhc3NiZWFtLmNvbXw0MDU2OTY1fC0xMTI5MDQ2NDY1>.
NAML<http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>




--
View this message in context: 
http://lucene.472066.n3.nabble.com/TooManyClauses-maxClauseCount-is-set-to-1024-tp4056965p4056972.html
Sent from the Solr - User mailing list archive at Nabble.com.

Reply via email to