lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From solr jay <solr...@gmail.com>
Subject Re: reindexed data on master not replicated to slave
Date Fri, 03 Jul 2009 04:16:51 GMT
it's nightly build of May 10. I'll try the latest.

Thanks,

J


On Thu, Jul 2, 2009 at 8:09 PM, Otis Gospodnetic <otis_gospodnetic@yahoo.com
> wrote:

>
> Jay,
>
> You didn't mention which version of Solr you are using.  It looks like some
> trunk or nightly version.  Maybe you can try the latest nightly?
>
>  Otis
> --
> Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
>
>
>
> ----- Original Message ----
> > From: solr jay <solrjay@gmail.com>
> > To: solr-user@lucene.apache.org
> > Sent: Thursday, July 2, 2009 9:14:48 PM
> > Subject: reindexed data on master not replicated to slave
> >
> > Hi,
> >
> > When index data were corrupted on master instance, I wanted to wipe out
> all
> > the index data and re-index everything. I was hoping the newly created
> index
> > data would be replicated to slaves, but it wasn't.
> >
> > Here are the steps I performed:
> >
> > 1. stop master
> > 2. delete the directory 'index'
> > 3. start master
> > 4. disable replication on master
> > 5. index all data from scratch
> > 6. enable replication on master
> >
> > It seemed from log file that the slave instances discovered that new
> index
> > are available and claimed that new index installed, and then trying to
> > update index properties, but looking into the index directory on slaves,
> you
> > will find that no index data files were updated or added, plus slaves
> keep
> > trying to get new index. Here are some from slave's log file:
> >
> > Jul 1, 2009 3:59:33 PM org.apache.solr.handler.SnapPuller
> fetchLatestIndex
> > INFO: Starting replication process
> > Jul 1, 2009 3:59:33 PM org.apache.solr.handler.SnapPuller
> fetchLatestIndex
> > INFO: Number of files in latest snapshot in master: 69
> > Jul 1, 2009 3:59:33 PM org.apache.solr.handler.SnapPuller
> fetchLatestIndex
> > INFO: Total time taken for download : 0 secs
> > Jul 1, 2009 3:59:33 PM org.apache.solr.handler.SnapPuller
> fetchLatestIndex
> > INFO: Conf files are not downloaded or are in sync
> > Jul 1, 2009 3:59:33 PM org.apache.solr.handler.SnapPuller
> modifyIndexProps
> > INFO: New index installed. Updating index properties...
> > Jul 1, 2009 4:00:33 PM org.apache.solr.handler.SnapPuller
> fetchLatestIndex
> > INFO: Master's version: 1246488421310, generation: 9
> > Jul 1, 2009 4:00:33 PM org.apache.solr.handler.SnapPuller
> fetchLatestIndex
> > INFO: Slave's version: 1246385166228, generation: 56
> > Jul 1, 2009 4:00:33 PM org.apache.solr.handler.SnapPuller
> fetchLatestIndex
> > INFO: Starting replication process
> > Jul 1, 2009 4:00:33 PM org.apache.solr.handler.SnapPuller
> fetchLatestIndex
> > INFO: Number of files in latest snapshot in master: 69
> > Jul 1, 2009 4:00:33 PM org.apache.solr.handler.SnapPuller
> fetchLatestIndex
> > INFO: Total time taken for download : 0 secs
> > Jul 1, 2009 4:00:33 PM org.apache.solr.handler.SnapPuller
> fetchLatestIndex
> > INFO: Conf files are not downloaded or are in sync
> > Jul 1, 2009 4:00:33 PM org.apache.solr.handler.SnapPuller
> modifyIndexProps
> > INFO: New index installed. Updating index properties...
> >
> >
> > Is this process incorrect, or it is a bug? If the process is incorrect,
> what
> > is the right process?
> >
> > Thanks,
> >
> > J
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message