Re: Synchronizing commit and optimize

2006-04-28 Thread Chris Hostetter
: The default value in the example installation is 3. Maybe : it wolud be a good idea to increase this, too. The example is really just designed to make it easy to see Solr in action really fast ... not to demonstrate any recommended configuration of the Jetty -- if we make too many tweaks to

Re: Synchronizing commit and optimize

2006-04-28 Thread Marcus Stratmann
Yonik Seeley wrote: >I think you are probably right about Jetty timing out the request. >Solr doesn't implement timeouts for requests, and I havent' seen this >behavior with Solr running on Resin. > >You could try another app server like Tomcat, or perhaps figure out of >the Jetty timeout is config

Re: Synchronizing commit and optimize

2006-04-24 Thread Yonik Seeley
On 4/24/06, Marcus Stratmann <[EMAIL PROTECTED]> wrote: > When I submit the command via curl, I > get the response "curl: (52) Empty reply from server" though solr is > still working I think you are probably right about Jetty timing out the request. Solr doesn't implement timeouts for requests, an

Synchronizing commit and optimize

2006-04-24 Thread Marcus Stratmann
Hello, when doing a commit or optimize the operation takes quite long (in my test case at least some minutes). When I submit the command via curl, I get the response "curl: (52) Empty reply from server" though solr is still working (as I can see from the process list and the admin interface). I tr