from "the bottom" and new docs are inserted on the top, so,
timeAllowed could cause that new docs never appear on the search results.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Shard-timeouts-on-large-1B-docs-Solr-cluster-tp3691229p3713263.html
Sent from the S
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
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 wrote:
>
> On Jan 26, 2012, at 1:28 PM, Jay Hill wrote:
>
> >
> > I've tried setting the following config in our de
On Jan 26, 2012, at 1:28 PM, Jay Hill wrote:
>
> I've tried setting the following config in our default req. handler:
> 2000
> 2000
>
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 abou
I'm on a project where we have 1B docs sharded across 20 servers. We're not
in production yet and we're doing load tests now. We're sending load to hit
100qps per server. As the load increases we're seeing query times
sporadically increasing to 10 seconds, 20 seconds, etc. at times. What
we're tryi
