This situation doesn't happen consistently. When we only ran the problematic core, the indexing took significant longer than usual(4hrs -> 11 hrs). It ran successful in the end. When we ran indexing for all cores at the same time, the problematic core never finished indexing such that we have to kill the process. This happened twice already. I'm running it parallel again to see if the problem still persists.
I also notice one thing, in the dataimport UI, the "Total Documents Processed" is missing from the problematic core and appeared for other cores. Does anyone know why? Thanks! Wen -----Original Message----- From: Lance Norskog [mailto:goks...@gmail.com] Sent: Friday, June 18, 2010 5:38 PM To: solr-user@lucene.apache.org Subject: Re: solr indexing takes a long time and is not reponsive to abort command Does this happen over and over? Does it happen every time? On Fri, Jun 18, 2010 at 1:19 PM, Ya-Wen Hsu <y...@eline.com> wrote: > I don’t see my last email showed in the mailing list so I’m sending again. > Below is the original email. > > Hi, > > I have multi-core solr setup. All cores finished indexing in reasonable time > but one. I look at the dataimport info for the one that’s hanging. The > process is still in busy state but no requests made or rows fetched. The > database side just showed the process is waiting for future command and is > doing nothing. The attempt to abort the process doesn’t really work. Does > anyone know what’s happening here? Thanks! > > Wen > -- Lance Norskog goks...@gmail.com
