On 9 February 2015 at 14:12, Yago Riveiro wrote:
> Now that I know what I’m looking for, in fact the wiki has an entry for
> formdataUploadLimitInKB, but doesn’t help too much if you don´t know that
> internal requests in solrcloud mode can be limited by this configuration.
Awesome. Change it t
Alex,
Now that I know what I’m looking for, in fact the wiki has an entry for
formdataUploadLimitInKB, but doesn’t help too much if you don´t know that
internal requests in solrcloud mode can be limited by this configuration.
+1 to Toke’s suggestion. In some cases the error messages are
Shawn Heisey [apa...@elyograg.org] wrote:
> You can change this value in solrconfig.xml by adding/modifying the
> formdataUploadLimitInKB attribute on the requestParsers tag.
Bingo. Checking on our server, I can see that we increased that value at some
point.
I am a big fan of error messages wit
Now that you have the (probable) answer, is there a particular page
you would have expected to see that at, when you did your own
research? Somewhere on the SolrCloud page? Or on the performance
tuning page?
Regards,
Alex.
P.s. It helps to mention that you have a SolrCloud setup when you face
i
Ok, now I understand the POST thing, is an internal query done between node.
I will put the formdataUploadLimitInKB in the solrconfig.xml.
I think that this should be documented in the wiki, is odd enough and is not an
error per se.
—
/Yago Riveiro
On Mon, Feb 9, 2015 at 6:03 PM, Alexa
On 2/9/2015 11:02 AM, Alexandre Rafalovitch wrote:
> You have a distributed collection (SolrCloud) setup, right? So, it
> seems that the request to collect the data from other nodes is hitting
> this exception. Though the error message is weird enough I would put
> only 80% probability on my explan
You have a distributed collection (SolrCloud) setup, right? So, it
seems that the request to collect the data from other nodes is hitting
this exception. Though the error message is weird enough I would put
only 80% probability on my explanation.
Were there any _other_ exceptions in the logs. On t
Ok, but why the error is related to POST limit if I don’t doing a POST request?
is a normal GET request …
—
/Yago Riveiro
On Mon, Feb 9, 2015 at 5:53 PM, Shawn Heisey wrote:
> On 2/9/2015 8:29 AM, yriveiro wrote:
>> I'm trying to retrieve from Solr a query in CSV format with around 500K
>> r
On 2/9/2015 8:29 AM, yriveiro 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. version=\"1.0\" encoding=\"UTF-8\"?>\n\n name=\"msg\">application/x-www-
Toke Eskildsen [t...@statsbiblioteket.dk] wrote:
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:
>> [...] application/x-www-form-urlencoded content length (6040427
>> bytes) exceeds upload
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:
> [...] application/x-www-form-urlencoded content length (6040427
> bytes) exceeds upload limit of 2048 KB [...]
I remember running into this
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.
application/x-www-form-urlencoded content
length
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 wrote:
> I’m using solr 4.6.1 with jetty and I have no ot
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=4000
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 sy
That's strange. The message seems to be about upload. You are querying Solr
for data it already has, right?
What does your query looks like?
Regards
Alex
On 9 Feb 2015 10:30 am, "yriveiro" wrote:
> I'm trying to retrieve from Solr a query in CSV format with around 500K
> registers and I al
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
17 matches
Mail list logo
