Hi, I think I did 2 changes at the same time: increased maxFormContentSize and zkClientTimeout (from 15s to 30s). When I restarted cluster there were no "ClusterState issues", but most probably due to increased zkClientTimeout and not maxFormContentSize. I did one more test with default value for maxFormContentSize (1M) and there were no issues either.
Regards. On 3 February 2013 22:16, Marcin Rzewucki <mrzewu...@gmail.com> wrote: > Hi, > > I set this: > <Call name="setAttribute"> > <Arg>org.eclipse.jetty.server.Request.maxFormContentSize</Arg> > <Arg>10485760</Arg> > </Call> > multipartUploadLimitInKB is set to 2MB in my case. The funny is that I did > change only in jetty.xml > I'll change this value back to 1MB and repeat test to check if this is the > reason. > Regards. > > > On 3 February 2013 21:26, Shawn Heisey <s...@elyograg.org> wrote: > >> On 2/3/2013 1:07 PM, Marcin Rzewucki wrote: >> >>> I'm loading in batches. 10 threads are reading json files and load to >>> Solr >>> by sending POST request (from couple of dozens to couple of hundreds docs >>> in 1 request). I had 1MB post request size, but when I changed it to 10MB >>> errors disappeared. I guess this could be the reason. >>> Regards. >>> >> >> I thought SOLR-4265 changed the whole way that Solr interacts with Jetty >> and set the max form size to 2MB within Solr. My reading says that you can >> now control the max POST size within solrconfig.xml - look for >> formdataUploadLimitInKB within the example solrconfig. >> >> I'm curious as to exactly how you changed the max size in jetty.xml. The >> typical way that you set maxFormContentSize is broken, but jetty 8.1.9 will >> fix that. Jetty 8.1.8 is what is currently included with Solr 4.1. See >> the following Jetty bug: >> >> https://bugs.eclipse.org/bugs/**show_bug.cgi?id=397130<https://bugs.eclipse.org/bugs/show_bug.cgi?id=397130> >> >> Thanks, >> Shawn >> >> >
