Francis, I'm not sure if I understood your email correctly, but I think you are saying you are indexing your DB content into a Solr index. If this is correct, here are things to look at: * is the java version the same on both machines (QA vs. PROD) * are the same java parameters being used on both machines * is the connection to the DB the same on both machines * are both the PROD and QA DB servers the same and are both DB instances the same ...
Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch ----- Original Message ---- > From: Francis Yakin <fya...@liquid.com> > To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org> > Sent: Friday, June 19, 2009 5:27:59 PM > Subject: Slowness during submit the index > > > We are experiencing slowness during reloading/resubmitting index from > Database > to the master. > > We have two environments: > > QA and Prod. > > The slowness is happened only in Production but not in QA. > > It only takes one hours to reload 2.5Mil indexes compare 5-6 hours to load > the > same size of index in Prod. > > I checked both the config files in QA and Prod, they are all identical, > except: > > > In QA: > false > In Prod: > true > > I believe that we use "http" protocol reload/submit the index from Database > to > Solr Master. > I did test copying big files thru network from database to the solr box, I > don't > see any issue. > > We are running solr 1.2 > > Any inputs will be much appreciated.
