Hi Erick, Scheduling the indexing job is not an issue. The question is how to push the index to other two slave instances while the polling from other two slave instance needs to be manipulated.
In the first option you proposed, I need to detect if the indexing job has completed, and force replication. In this case, the polling is not enabled In the second option, I also need to detect the status of the indexing job and enable / disable polling from the two slave machine. Is there any API to do it? In addition, It looks like I also need to make this job to poll the indexing machine to check a new version of index? I might be able to get around this requirement by using a scheduled job since I know roughly how long the indexing job is going to take, and execute the job well after the indexing job should be finished. Thanks Thanks On Fri, Jul 10, 2015 at 3:57 PM, Erick Erickson <erickerick...@gmail.com> wrote: > bq: The re-indexing is going to be every 4 hours or even every 2 hours a > day, so > it is not rare. Manually managing replication is not an option > > Why not? Couldn't this all be done from a shell script run via a cron job? > > On Fri, Jul 10, 2015 at 11:03 AM, wwang525 <wwang...@gmail.com> wrote: > > Hi Erick, > > > > It is Solr 4.7. For the time being, we are considering the old style > > master/slave configuration. > > > > The re-indexing is going to be every 4 hours or even every 2 hours a > day, so > > it is not rare. Manually managing replication is not an option. Is there > any > > other easy-to-manage option ? > > > > Thanks > > > > > > > > -- > > View this message in context: > http://lucene.472066.n3.nabble.com/Planning-Solr-migration-to-production-clean-and-autoSoftCommit-tp4216736p4216744.html > > Sent from the Solr - User mailing list archive at Nabble.com. >
