We also see extreme slowness using Solr 3.6 when trying to commit a delete. We also get hangs. We do 1 commit at most a week. Rebuilding from scratching using DIH works fine and has never hung.
Bill Bell Sent from mobile On Apr 27, 2012, at 5:59 PM, "mav.p...@holidaylettings.co.uk" <mav.p...@holidaylettings.co.uk> wrote: > Thanks for the reply > > The client expects a response within 2 minutes and after that will report > an error. When we build fresh it seems to work and the operation takes a > second or two to complete. Once it gets to a stage it hangs it simply > won't accept any further commits. I did an index check and all was ok. > > I don¹t see any major commit happening at any time, it seems to just > hang. Even starting up and shutting down takes ages. > > We make 3 - 4 commits a day. > > We use solr 3.5 > > No autocommit > > > > On 28/04/2012 00:56, "Yonik Seeley" <yo...@lucidimagination.com> wrote: > >> On Fri, Apr 27, 2012 at 9:18 AM, mav.p...@holidaylettings.co.uk >> <mav.p...@holidaylettings.co.uk> wrote: >>> We have an index of about 3.5gb which seems to work fine until it >>> suddenly stops accepting new commits. >>> >>> Users can still search on the front end but nothing new can be >>> committed and it always times out on commit. >>> >>> Any ideas? >> >> Perhaps the commit happens to cause a major merge which may take a >> long time (and solr isn't going to allow overlapping commits). >> How long does a commit request take to time out? >> >> What Solr version is this? Do you have any kind of auto-commit set >> up? How often are you manually committing? >> >> -Yonik >> lucenerevolution.com - Lucene/Solr Open Source Search Conference. >> Boston May 7-10 >
