That section of the docs says "Replica databases can be queried but cannot be updated by applications." In my experience read-only queries are fine, but you'll see an error if you try any updates.
Rob, where do you see that "replica last updated" message? In the admin UI replication status, or somewhere else? Have you checked the output from https://docs.marklogic.com/xdmp:database-nonblocking-timestamp or https://docs.marklogic.com/xdmp:request-timestamp in qconsole? Do they both advance? -- Mike > On 6 Feb 2015, at 06:52 , Danny Sinang <[email protected]> wrote: > > Hi Rob, > > I found this in an old email from ML Support : > > Are you trying to query or connect to a active replica database? > > This isn't supported in MarkLogic 7 and it is explained and pointed out in > our documentation. > (http://docs.marklogic.com/guide/database-replication/dbrep_intro#id_75473) > > To query and / or update you need to break up your replication first and roll > back to latest available timestamp. > > > > > > Regards, > Danny > > > > > On Fri, Feb 6, 2015 at 9:27 AM, Whitby, Rob <[email protected]> wrote: > Hi, > > I’m using qconsole to query a replica database (a slave using database > replication). > > It seems qconsole keeps executing requests at the same timestamp, so doesn’t > see replication updates. The “Replica last updated at” message never updates > even though I know replication is happening. > > Is that expected behaviour? > > (this on 7.0-4.3) > > Thanks > Rob > > > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general > > > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
