Oops... my previous replies accidentally went off-list. I'll cut-n-paste below.
OK, so it looks like there is probably no bug here - it's simply that commits can sometimes take a long time and updates were blocked during that time (and would have succeeded eventually except the jetty timeout was not set long enough). Things are better in trunk (4.0) with soft commits and updates that can proceed concurrently with commits. -Yonik lucenerevolution.com - Lucene/Solr Open Source Search Conference. Boston May 7-10 On Thu, Mar 29, 2012 at 3:11 PM, Rafal Gwizdala <rafal.gwizd...@gmail.com> wrote: > You're right, this is not default Jetty from Solr - I configured it from > scratch and then added Solr. > Previously I had autocommit enabled and also did commit on every update so > this might also contribute to the problem. Now I disabled it and made the > updates less frequent. > If the autocommit is allowed to happen together with 'manual' commit on > update then there could be simultaneous commits, which now shouldn't happen > - there will be at most one update/commit active at a time. > Request timeout is default for jetty, but don't know what's that value. > > Best regards > RG > I wrote: On Thu, Mar 29, 2012 at 2:25 PM, Rafal Gwizdala <rafal.gwizd...@gmail.com> wrote: > Yonik, I didn't say there was an update request active at the moment the > thread dump was made, only that previous update requests failed with a > timeout. So maybe this is the missing piece. > I didn't enable nio with Jetty, probably it's there by default. Not with the jetty that comes with Solr. bq. If solr hangs next time I'll try to make a thread dump when the update request is waiting for completion. Great! We need to see where it's hanging! Also, how long did the request take to time out? Do you have auto-commit enabled? In the 3x series, updates will block while commits are in progress, so timeouts can happen if they are set too short (and it seems like maybe you aren't using the Jetty from Solr, so the configuration may not be ideal).
