i'm changing the params to socketTimeout and connTimeout and will test this afternoon. client timeout was actually removed today, which helped a bit.
what about the other params, "timeAllowed" and "partialResults". my expectation was that these were specifically for distributed search, meaning if a response wasn't received w/in the timeAllowed, and if partialResults is true, then that shard would not be waited on for results. is that correct? thanks, -jay On Thu, Jan 26, 2012 at 2:23 PM, Jay Hill <jayallenh...@gmail.com> wrote: > We're on the trunk: > 4.0-2011-10-26_08-46-59 1189079 - hudson - 2011-10-26 08:51:47 > > Client timeouts are set to 4 seconds. > > Thanks, > -Jay > > > On Thu, Jan 26, 2012 at 1:40 PM, Mark Miller <markrmil...@gmail.com>wrote: > >> >> On Jan 26, 2012, at 1:28 PM, Jay Hill wrote: >> >> > >> > I've tried setting the following config in our default req. handler: >> > <int name="shard-socket-timeout">2000</int> >> > <int name="shard-connection-timeout">2000</int> >> > >> >> >> What version are you using Jay? At least on trunk, I took a look and it >> appears at some point these where renamed to socketTimeout and connTimeout. >> >> What about a timeout on your clients? >> >> - Mark Miller >> lucidimagination.com >> >> >
