RSolr::Error::Http (RSolr::Error::Http - 413 Request Entity Too Large

[Thorsten Müller]

I have a relative large query, because we use many facet fields (about 150).

All queries work as long as I don't query for all facets at once.
If I add them all, I get

RSolr::Error::Http (RSolr::Error::Http - 413 Request Entity Too Large

This is on my OSX development setup, where I start solr from commandline with:
java -Dsolr.solr.home=. -jar start.jar

This folder has a simplified copy of the solr example folder. Worked well enough so far.

I'm not sure if this is an rsolr issue or comes from Solr itself. (Or something in between used by rsolr to process the query)
I changed from using rsolr.get to rsolr.post, but no difference

If I split the facet fields and run multiple queries, everything works fine. I could keep it that way but not sure about performance issues. On my developer machine Solr's caching seems to work here and the later queries are fast enough.

First part of stacktrace:

rsolr (1.0.8) lib/rsolr/client.rb:230:in `adapt_response'
rsolr (1.0.8) lib/rsolr/client.rb:167:in `execute'
rsolr (1.0.8) lib/rsolr/client.rb:161:in `send_and_receive'
(eval):2:in `post'
app/controllers/admin/searches_controller.rb:122:in `create'
actionpack (3.0.9) lib/action_controller/metal/implicit_render.rb:4:in `send_action'
actionpack (3.0.9) lib/abstract_controller/base.rb:150:in `process_action'
actionpack (3.0.9) lib/action_controller/metal/rendering.rb:11:in `process_action'
actionpack (3.0.9) lib/abstract_controller/callbacks.rb:18:in `block in process_action'

If I run the long query with curl, I have similar problems. In case of curl I get no response at all. (While the shorter queries work)
So this seems to be a problem with the general setup and limitations of this machine? There seems to be some bottleneck.

I could trick around that partly by either as I do now splitting the query or using shorter field names.
But I would prefer to properly evaluate all options.

I installed the whole thing on our Linux Testserver and query over that address, I get the same result. So it seems it's not OSX specific.

Are there any setup options for either rsolr, ruby, rails or solr (via start.jar) that would increase the possible request size?

[matt mitchell]

Thorsten,

This is caused by a configuration setting in Jetty. Here are a couple of links that may help:

https://groups.google.com/forum/?fromgroups=#!topic/google-appengine-java/SI1XwiO4Fzw

http://issues.opennms.org/browse/NMS-4815

http://blog.richeton.com/2010/03/11/set-jetty-buffer-size-maven/#more-897

Hope this helps. Let me know what happens.

- Matt