In a database replication setup, it is necessary to apply index changes on the replica first and then apply them on the master. You will need to do a forced re-indexing on the master to get the replica into a consistent state with the index changes.
See: http://docs.marklogic.com/guide/database-replication/dbrep_intro#id_27654 Gene Thomas (Elroy) AIS EIE MLCoE From: [email protected] [mailto:[email protected]] On Behalf Of Ankit Bhardwaj Sent: Monday, April 25, 2016 4:53 AM To: [email protected] Subject: [MarkLogic Dev General] Replicas not getting reindexed Hi, I have to change few index settings on the production environment. While testing it, I changed the settings on "Master" first. As expected, indexing started automatically. After that I changed the index settings on replica with an expectation that indexing will start. But it does not started. I also tried manually triggering the re-indexing (from MarkLogic Admin Console) but it didn't start. I have got good amount of data (around 500,000 documents) in my database. So, it can't be the case that re-indexing happened and I didn't noticed. I also checked the logs. They also haven't got anything. Can you please suggest that what is going wrong here? Why I am not able to trigger re-indexing on replica? Thanks, Ankit Bhardwaj This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna
_______________________________________________ General mailing list [email protected] Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
