Razorblade wrote: > > > Hi All, > today I got my hosting suspended because of a process related with > Zend_Search_Lucene. > > The only thing they told me is the stack trace of the process that caused > the abuse, > but I cannot recognize which was the request that caused the issue. > > So my question is a bit generic: > > if I have cpu usage problem with Zend_Search_Lucene, > what could be a common error that I might have done speaking about query > the index or add a document to the index? > > Thanks for all suggestions > > Sergio >
Hi, I think it could be caused because when the resultset includes more than 1024 rows (default) but usually the script throw an exception. I managed it with $currentResultSetLimit = Zend_Search_Lucene::getResultSetLimit(); Zend_Search_Lucene::setResultSetLimit($newLimit); Bye -- View this message in context: http://zend-framework-community.634137.n4.nabble.com/Zend-Search-Lucene-and-CPU-abuse-tp3324604p3326115.html Sent from the Zend Framework mailing list archive at Nabble.com.
