the stack trace




ERROR - localhost - 2015-02-09 15:05:03.698; 
org.apache.solr.common.SolrException; 
org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Expected 
mime type application/octet-stream but got application/xml. <?xml version="1.0" 
encoding="UTF-8"?>

<response>

<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>

</response>




        at 
org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:459)

        at 
org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:199)

        at 
org.apache.solr.client.solrj.impl.LBHttpSolrServer.request(LBHttpSolrServer.java:285)

        at 
org.apache.solr.handler.component.HttpShardHandlerFactory.makeLoadBalancedRequest(HttpShardHandlerFactory.java:214)

        at 
org.apache.solr.handler.component.HttpShardHandler$1.call(HttpShardHandler.java:161)

        at 
org.apache.solr.handler.component.HttpShardHandler$1.call(HttpShardHandler.java:118)

        at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)

        at java.util.concurrent.FutureTask.run(Unknown Source)

        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

        at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)

        at java.util.concurrent.FutureTask.run(Unknown Source)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

        at java.lang.Thread.run(Unknown Source)




—
/Yago Riveiro

On Mon, Feb 9, 2015 at 4:36 PM, Alexandre Rafalovitch <arafa...@gmail.com>
wrote:

> Is there an exception stack trace on the server side in the logs?
> Might tell a lot more of the story.
> Regards,
>    Alex.
> ----
> Sign up for my Solr resources newsletter at http://www.solr-start.com/
> On 9 February 2015 at 11:11, Yago Riveiro <yago.rive...@gmail.com> wrote:
>> I’m using solr 4.6.1 with jetty and I have no other piece of custom software 
>> that can raise this issue.
>>
>>
>>
>>
>> The query is something like this:
>>
>>
>>
>>
>> http://localhost:8983/solr/collection-1/query?q=datetime:[2015-02-01T00:00:00Z%20TO%202015-02-01T23:59:59Z]&fl=field_1&wt=csv&csv.header=false&rows=400000
>>
>>
>>
>>
>> With json format the same error happen. I’m not uploading nothing, and this 
>> is the first thing that I didn’t understand from this error.
>>
>>
>>
>>
>> I know that are a lot of records, but my infrastructure can handle this and 
>> this csv is the input for other application.
>>
>>
>> —
>> /Yago Riveiro
>>
>> On Mon, Feb 9, 2015 at 4:03 PM, Yonik Seeley <ysee...@gmail.com> wrote:
>>
>>> Hmmm, that's interesting...
>>> It looks like a container (jetty/tomcat or whatever) configuration
>>> limit somewhere.  I'd only expect this error from Solr when trying to
>>> send something really large though - notice "upload" in the error.  Is
>>> this error message really from Solr or another piece of your system?
>>> If this error message is from Solr, please open a JIRA issue so this
>>> doesn't get lost.
>>> -Yonik
>>> 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.

Reply via email to