Solr search engine is used in the project. When too many FQ filtering conditions are found, the query will report an exception, non OK status: 413, message: full head. This exception is caused by too many conditions during the query, resulting in insufficient head of the request

Solution: new httpsolrclient(). Query(), which is a get request by default. The number of conditions that a get request can carry is relatively small. It needs to be specified as a post request, that is, new httpsolrclient(). Query (query, solrrequest. Method. Post). In this way, the number of requests is relatively large. If it is not enough, the configuration file of Solr needs to be modified. The file path is solr-5.1.0/server/solr/configsets/, The & lt; maxBooleanClauses> 1024</ maxBooleanClauses> Attribute, increase 1024 to

Similar Posts:

• [Solved] Solr Error: org.apache.solr.common.SolrException: undefined field text
• org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to initialize component [Connector[HTTP/1.1-8080]]
• solr Error: SolrException:org.apache.solr.common.SolrException: Error opening new searcher Please check your logs for more information
• What does HTTP status code 304 mean
• Laravel route cannot be accessed, report 404, no query results for model
• java.io.IOException: Server returned HTTP response code: 405 for URL:
• How to Use awk to Analyze Nginx Log
• Solution of 405 not allowed error in nginx
• MYSQL Startup Error: [ERROR] Aria engine is not enabled or did not start. The Aria engine must be enabled to
• [Solved] Linux Start solr Error: Your Max Processes Limit is currently 31202. It should be set to 65000 to avoid operational disruption.