In the 3.6 world, LukeRequestHandler does some...er...really expensive things when you click into the admin/schema browser. This is _much_ better in trunk BTW.
So, as Yonik says, LukeRequestHandler probably accounts for one of the threads. Does this occur when nobody is playing around with the admin handler? Erick On Sat, Apr 28, 2012 at 10:03 AM, Yonik Seeley <yo...@lucidimagination.com> wrote: > On Sat, Apr 28, 2012 at 7:02 AM, mav.p...@holidaylettings.co.uk > <mav.p...@holidaylettings.co.uk> wrote: >> Hi, >> >> This is what the thread dump looks like. >> >> Any ideas? > > Looks like the thread taking up CPU is in LukeRequestHandler > >> 1062730578@qtp-1535043768-5' Id=16, RUNNABLE on lock=, total cpu >> time=16156160.0000ms user time=16153110.0000msat >> org.apache.solr.handler.admin.LukeRequestHandler.getIndexedFieldsInfo(LukeR >> equestHandler.java:320) > > That probably accounts for the 1 CPU doing things... but it's not > clear at all why commits are failing. > > Perhaps the commit is succeeding, but the client is just not waiting > long enough for it to complete? > > -Yonik > lucenerevolution.com - Lucene/Solr Open Source Search Conference. > Boston May 7-10
