Bryan and Geert,

Thank you for your info.  I have resumed my efforts trying to get local disk 
failover to work now since the holiday is over, but I still am having 
difficulty.  If anyone can shed any light I'd sure appreciate it.


1.      I have created a failover for Security DB as Bryan suggests, but the 
results are the same. Shutting down the primary shuts down all secondaries

2.      Geert has suggested that I also fail-over the forests for Modules, 
Triggers, and Schemas

3.      The documentation speaks (in a roundabout way) about App-Services and 
Meters too....

It is very confusing to know what is the minimum set of "built-in" databases 
that I need to create a failover for. In my little prototype I have no modules, 
triggers, or schemas, so I wouldn't think I would need to set these up for 
failover, but I don't know what MarkLogic is depending on internally.   Then 
there's App-Services, Meters, Extensions, Fab, Last-Login, etc.  Any idea on 
what is the minimal set of databases that MarkLogic really needs to have access 
to in order to run?

It would seem to me that MarkLogic would publish a definitive list these 
necessary built-in databases so that fail over allows a server to run 
autonomously.  I would love to see this list included in the local disk 
clustering and failover set up docs.

Thanks for any help...

Paul Vanderveen

From: [email protected] 
[mailto:[email protected]] On Behalf Of Clark, Bryan
Sent: Wednesday, December 23, 2015 4:32 PM
To: '[email protected]' <[email protected]>
Subject: Re: [MarkLogic Dev General] Shutting down initial host causes cluster 
to stop

Paul,

Do you have Security forest replicated to Host 2 or Host 3?

You do need to have Security database online to continue working - the 'shared 
nothing' architecture does not extend to Security and some system features & 
facilities that leverage system databases like Documents, Meters, etc.; we are 
a local disk shop, and use Local Disk Forest Failover to distribute/failover-to 
the MarkLogic "system" databases as part of our default cluster provisioning.

Cheers,
Bryan

From: 
[email protected]<mailto:[email protected]>
 [mailto:[email protected]] On Behalf Of Paul Vanderveen
Sent: Wednesday, December 23, 2015 6:21 PM
To: [email protected]<mailto:[email protected]>
Subject: [MarkLogic Dev General] Shutting down initial host causes cluster to 
stop

I created a 3 host cluster in order to better understand clustering


1.      Host 1 Has a forest that is replicated in Host 2 and 3. The forests are 
at "sync replicating"

2.      I disable the network from Host 1, so it is essentially removed

3.      The log reports failover, but....

I can't do anything on Host 2 and 3 while Host 1 is offline.  Not even the 
admin page.  This seems wrong.  I thought all hosts shared essential data.

I can shut down Host 2 or 3 and everything including forest failover works 
fine, but shutting down Host 1 seems to bring the whole cluster down.   It was 
my understanding that there is no "master" host, so I would think that I could 
shut down any host and the others would take up the slack

Am I doing something wrong?  Is this expected results?

Paul Vanderveen



Confidentiality Notice: This electronic message transmission, including any 
attachment(s), may contain confidential, proprietary, or privileged information 
from Chemical Abstracts Service ("CAS"), a division of the American Chemical 
Society ("ACS"). If you have received this transmission in error, be advised 
that any disclosure, copying, distribution, or use of the contents of this 
information is strictly prohibited. Please destroy all copies of the message 
and contact the sender immediately by either replying to this message or 
calling 614-447-3600.
_______________________________________________
General mailing list
[email protected]
Manage your subscription at: 
http://developer.marklogic.com/mailman/listinfo/general

Reply via email to