I finally had the chance to apply this locally and try it out. I have not been able to get this time out business to kick in, though. Here is what I did so far, after applying the patch, and clean dist and deployment of solr war.
I set up 2 Solr instances (actually 1 Jetty with 2 Solr homes defined via JNDI). Identical schema, each index with 100K docs.
I then hit one of the instances, specifying both shards and asked for q=title:a* (expensive query), while using timeAllowed=1, like this:
....Aaaarg, I see one problem. That "timeAllowed" is specified as "timeallowed":
[otis@localhost SOLR-502]$ grep TIME_ALLOW SOLR-502.patch | head -1
+ public static final String TIME_ALLOWED = "timeallowed";
Sean, I think this should be camelCase, too.
OK, so changing that:
However, I am still unable to get the timeout to happen. I see QTime of 257 in the response, clearly above timeallowed=1. If timeallowed=1, should I ever be seeing QTime over 1?
<result name="response" numFound="50936" start="0">
I also grepped the output for "partial" and never find anything. Am I doing something wrong?
I also see the latest
SOLR-502.patch still has some print statements, so I looked at stdout, but nothing is getting printed there.
I'll see if I can trace this, but if I did something wrong or see a bug in your code, I'm all eyes.