Change the replica first, then the master. Each will index independently. -- Mike
> On Sep 28, 2014, at 23:04, [email protected] wrote: > > I tried to search for the answer, but couldn't find it, I would appreciate if > any of you could direct me to the correct chunk of documentation to find this > out: > > We have two node ML7 setup where one of the nodes is master and other slave > using database replication matched by the database name. (This is NOT > flexible replication) > > We execute queries to both hosts 24/7 but obviously write only to the primary > one. > > We often need to add new indexes to the system and the (multi part) question > is: > > 1. Does ML replicate the index definitions between hosts? > 2. Does ML replicate the indexes themselves between the hosts? > 3. What's the correct procedure to add a new index in this setup? > > We currently add the indexes by hand, starting from the slave. We noticed > that the slave does not initiate automatic reindexing, even though we have > "reindexer enable" set to true and figured it's better to add the new index > to slave first so that it will be there when the primary starts reindexing. > > So, is it required at all to add the indexes first to slave, or will ML take > care of the configuration changes via the replication also or does that > include only data? > > Ville > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
