Bootstrap to replicate internals fails on Modules DB

[jamsilvia]

When bootstrapping and specifying to create internal replicas, the process hangs while trying to add replicas to the internal Modules database.

1. ./ml boostrap --replicate-internals --nr-replicas=1
2. tail -f 8000_ErrorLog.txt
3. When the processing gets to Modules DB, the Modules DB gets reported as going to "middle closing", and holds there.
4. Once Roxy process times out and exits, the Modules DB completes closing and reopens with the replica attached.

When trying to debug this, it looks like the Modules DB is waiting because there is an active query running against it. The App-Services server is using it as the modules DB, and at the same time, the App-Services server is servicing the eval request from Roxy. Changing the modules database for App-Services to something else (e.g. filesystem) before bootstrap avoids the issue.

This seems to be related to the fact that at some point MarkLogic delivered the App-Services server with a change in modules from "filesystem" to "Modules".

Which Operating System are you using?
CentOS/RHEL 6, CentOS/RHEL 7, Mac OSX

Which version of MarkLogic are you using?
8.0-5.2, 9.1-1, 9.2

Which version of Roxy are you using (see version.txt)?
1.7.6, 1.7.7

[grtjn]

I don't think the fact app-services is attached to modules is very new. Replicate internals does pre-date the features to keep track of replica forest changes.

It does ring a bell to me by the way. I thought i made a change to setup.xqy to fight something similar..

[tdiepenbrock]

I can validate this is an issue. I had to remove Modules from the system-dbs property in order to get bootstrap to work. It also sometimes gets hung up on Security. I finally settled on a solution in app_specific.rb where I bootstrap replicas for Security first, then the rest of the internals.