e type of PC/MAC you're using, you
> can use WireShark to look at active http header (sent and received) that
> are being created for the request.
> > https://www.wireshark.org/
> > I don't have any financial interest in them, but the stuff works!
> > Steve
&
t in them, but the stuff works!
> Steve
>
>> Date: Sun, 23 Nov 2014 20:47:05 +0100
>> Subject: Re: Too much data after closed for HttpChannelOverHttp
>> From: h.benoud...@gmail.com
>> To: solr-user@lucene.apache.org
>>
>> Actually I'm using a php client
ve
> Date: Sun, 23 Nov 2014 20:47:05 +0100
> Subject: Re: Too much data after closed for HttpChannelOverHttp
> From: h.benoud...@gmail.com
> To: solr-user@lucene.apache.org
>
> Actually I'm using a php client (I think it sends a HTTP request to Solr),
> but you're ri
Actually I'm using a php client (I think it sends a HTTP request to Solr),
but you're right tomorrow once I'll get to the office, I'll set chunk size
to a smaller value, and will tell you if that was the reason.
Thanks.
2014-11-23 19:35 GMT+01:00 Alexandre Rafalovitch :
> Most probably just a re
Most probably just a request that's too large. Have you tried dropping
down to 500 items and seeing what happens?
Are you using SolrJ to send content to Solr? Or a direct HTTP request?
Regards,
Alex.
P.s. You may also find it useful to read up on the Solr commit and
hard vs. soft commits. Chec
