Well, your commits may have to wait until any merges are done, which _may_ be merging your entire index into a single segment. Possibly this could take more than 60 seconds.
_How_ are you doing this? DIH? SolrJ? post.jar? Best Erick On Tue, Feb 19, 2013 at 8:00 PM, Siping Liu <liu01...@gmail.com> wrote: > Thanks for the quick response. It's Solr 3.4. I'm pretty sure we get plenty > memory. > > > > On Tue, Feb 19, 2013 at 7:50 PM, Alexandre Rafalovitch > <arafa...@gmail.com>wrote: > > > Which version of Solr? > > Are you sure you did not run out of memory half way through import? > > > > Regards, > > Alex. > > > > Personal blog: http://blog.outerthoughts.com/ > > LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch > > - Time is the quality of nature that keeps events from happening all at > > once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) > > > > > > On Tue, Feb 19, 2013 at 7:44 PM, Siping Liu <liu01...@gmail.com> wrote: > > > > > Hi, > > > we have an index with 2mil documents in it. From time to time we > rewrite > > > about 1/10 of the documents (just under 200k). No autocommit. At the > end > > we > > > a single commit and got time out after 60 sec. My questions are: > > > 1. is it normal to have the commit of this size takes more than 1min? I > > > know it's probably depend on the server ... > > > 2. I know there're a few parameters I can set in CommonsHttpSolrServer > > > class: setConnectionManagerTimeout(), setConnectionTimeout(), > > > setSoTimeout(). Which should I use? > > > > > > TIA > > > > > >
