Are you sure that this parameter concerns /update requests? On the one hand, it says that it "specides the max size of form data (application/x-www-form-urlencoded) sent via POST. You can use POST to pass request parameters not fitting into URL"
and on the other hand, I see the my bulks are as big as 7mb in some cases and I dont' get any error for these. I now write to log the bulk size in kbs of each bulk and the time it took for the solrclient to get a status reply. I tried to correlate between spikes in these metrics and these warnings - but seems that there is no relation. I'm indexing again right now to try to reproduce the problem. I'm seeing these warnings but need to wait for the end of the indexing to see if there is any dataloss and if the docs that got lost correlate by time to these warning. would be glad to here more ideas about this warning and this problem. Shawn Heisey-2 wrote > On 8/4/2015 8:06 AM, adfel70 wrote: >> I saw this post: >> http://lucene.472066.n3.nabble.com/Too-much-data-after-closed-for-HttpChannelOverHttp-td4170459.html >> >> I tried reducing the bulk size from 1000 to 200 as the post suggests >> (didn't >> go to runing each doc in a seperate .add call yet), with no success. In >> this >> try I'm getting the same WARNING, but now I also have regular errors such >> as >> NoHttpResponseExcpeption which is fine because the client also gets an >> error >> and I can handle this. > > How big are those docs? Is there any chance that the index request from > those 200 docs would exceed 2 megabytes? That's the default size limit > on a POST request. > > In your solrconfig.xml, there is a requestDispatcher section, which has > a requestParsers tag inside it. In the requestParsers tag you can > change the formdataUploadLimitInKB parameter, which defaults to 2048. > In 3.x, this would have been controlled by the container config, but > since about 4.1, Solr can configure it directly. I have changed mine to > 32768, so I can be SURE it's big enough for anything I might throw at > it, but not so big that incredibly massive requests can be sent. > > Thanks, > Shawn -- View this message in context: http://lucene.472066.n3.nabble.com/serious-data-loss-bug-in-correlation-with-too-much-data-after-closed-tp4220723p4221300.html Sent from the Solr - User mailing list archive at Nabble.com.
