Yago, I can't speak to the specific error. However, that's quite a lot of rows from one request. Solr and Lucene need to build that in memory, which can create all kinds of heap issues. You could try using start to page through the rows, but you'll run into a problem known as deep paging.
In short rows/start are optimized for users that want to page through the top couple of pages of results. Performance gets progressively worse as you go through the results on as Lucene needs to build up all the search results on every subsequent request. The solution to problem "I want to pull every/many results from my index" is to use cursors. Hossman has a good article linked here. I wrote one too, here these might help: https://lucidworks.com/blog/coming-soon-to-solr-efficient-cursor-based-iteration-of-large-result-sets/ http://opensourceconnections.com/blog/2014/07/13/reindexing-collections-with-solrs-cursor-support/ Further, you probably want to set an explicit max on the number of rows for your Solr cluster to prevent folks from causing your Solr to collapse because they specified a billion rows. Hope that helps, -Doug On Mon, Feb 9, 2015 at 10:29 AM, yriveiro <yago.rive...@gmail.com> wrote: > I'm trying to retrieve from Solr a query in CSV format with around 500K > registers and I always get this error: > > "Expected mime type application/octet-stream but got application/xml. <?xml > version=\"1.0\" encoding=\"UTF-8\"?>\n<response>\n<lst name=\"error\"><str > name=\"msg\">application/x-www-form-urlencoded content length (6040427 > bytes) exceeds upload limit of 2048 KB</str><int > name=\"code\">400</int></lst>\n</response>\n" > > If the rows value is lower, like 50000 the query doesn't fail. > > What I'm doing wrong? > > > > ----- > Best regards > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Query-always-fail-if-row-value-is-too-high-tp4185047.html > Sent from the Solr - User mailing list archive at Nabble.com. > -- Doug Turnbull Search Relevance Lead OpenSource Connections <http://o19s.com>
