We're using Solr Cloud as a component of Cloudera's CDH5.5. A colleague built an application that POSTing long queries that exceed the default maxFormContentSize
(200,000 bytes). I ran a ps -ef
on one of the cluster nodes, and see that Solr's started with a lot of options:
usr/java/jdk1.7.0_67-cloudera/bin/java
[...etc...]
-Djetty.port=8983
[...etc...]
org.apache.catalina.startup.Bootstrap start
To increase the size of queries that Solr can handle, I'd like to increase the maxFormContentSize
. If we managed Solr through the command-line, I imagine we'd be able to pass an argument like this:
-Dorg.eclipse.jetty.server.Request.maxFormContentSize=500000
But, since we're using Cloudera Manager to control/monitor our services, it seems that the configuration change should be made there. I notice that Cloudera Manager has a "Java Configuration Options for Solr Server": setting which says:
These arguments will be passed as part of the Java command line. Commonly, garbage collection flags or extra debugging flags would be passed here.
I'd like to know:
- is
org.eclipse.jetty.server.Request.maxFormContentSize
the right parameter to change to increase the POST size for Solr? - is "Java Configuration Options for Solr Server" in Cloudera Manager the right place to set this?
- if so, would I simply add
-Dorg.eclipse.jetty.server.Request.maxFormContentSize=500000
to the "Java Configuration Options for Solr Server"?
And if I'm on the wrong track, how can we configure a CDH5.5 managed to accept larger-than-the-default queries?
– Gerry King Mar 23 '16 at 14:33