The replication lag needs to be determined on the master site (not the DR site).
In the admin console, under [YOUR-DATABASE] > Database Replication, you can see "Pending Frames," "Pending Bytes," and "Pending Lag" per forest. If you want to get at it programmatically, you can use xdmp:forest-status($forst-id), which has element /forest-status/replication with <pending-frames>, <pending-bytes>, and <pending-lag> children. Markus On Wed, Nov 18, 2015 at 3:05 PM, Sudheer Yalaverthi < [email protected]> wrote: > There is a database-replication-receive-time element in the forest status > XML. I am not sure if this is the right parameter to indicate how far the > replica is lagging behind primary. > > Can anybody share your thoughts? > > > > > > -Sudheer > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Sudheer Yalaverthi > *Sent:* Wednesday, November 18, 2015 4:01 PM > *To:* MarkLogic Developer Discussion > *Subject:* [MarkLogic Dev General] How to find the replication lag status? > > > > Hi, > > > > > > Is there a way to identify the replication status(basically how far the > replica is lagging behind the primary) of each of the forests in a > database? My intention is to identify how far the replica database is > lagging behind the primary database and if the lag limit exceeds, I would > like to generate a log in the error log file. > > > > > > > > Regards, > > Sudheer Yalaverthi > > NoSQL Engineer | BigData Engineering Team > > Deutsche Bank - Cary, USA > > > > > > --- > This communication may contain confidential and/or privileged information. > If you are not the intended recipient (or have received this communication > in error) please notify the sender immediately and destroy this > communication. Any unauthorized copying, disclosure or distribution of the > material in this communication is strictly forbidden. > > Deutsche Bank does not render legal or tax advice, and the information > contained in this communication should not be regarded as such. > > > --- > This communication may contain confidential and/or privileged information. > If you are not the intended recipient (or have received this communication > in error) please notify the sender immediately and destroy this > communication. Any unauthorized copying, disclosure or distribution of the > material in this communication is strictly forbidden. > > Deutsche Bank does not render legal or tax advice, and the information > contained in this communication should not be regarded as such. > > _______________________________________________ > General mailing list > [email protected] > Manage your subscription at: > http://developer.marklogic.com/mailman/listinfo/general > > -- Markus Flatscher Consultant | Avalon Consulting, LLC [email protected] LinkedIn: http://www.linkedin.com/company/avalon-consulting-llc Google+: http://www.google.com/+AvalonConsultingLLC Twitter: https://twitter.com/avalonconsult
_______________________________________________ General mailing list [email protected] Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
