[MarkLogic Dev General] Issue with Registering Resoruce extenion in cluster
Erik.Hennum at marklogic.com
Wed Mar 11 16:35:58 PDT 2015
Are you sending requests to all three nodes?
One typical approach for a three-node cluster is to put most of the forests on two of the nodes (the dnodes) and serve requests on one node (the enode).
Anyway, whether you have one enode or several enodes, the enodes should all share the same modules database. You should only have to install the resource service extension once.
Can you expand on how the extension was not working as expected before you installed on the other nodes?
From: general-bounces at developer.marklogic.com [general-bounces at developer.marklogic.com] on behalf of Gnanaprakash.Bodireddy at cognizant.com [Gnanaprakash.Bodireddy at cognizant.com]
Sent: Tuesday, March 10, 2015 3:38 AM
To: general at developer.marklogic.com
Subject: [MarkLogic Dev General] Issue with Registering Resoruce extenion in cluster
I am facing an issue with resource extensions in cluster environment.
We are having 3 node cluster and we are registering our resource extension to node 1 which is our bootstrap node.
The resource extension is working without issue on node 1 where we registered but not working as expected on other 2 nodes.
/v1/config/resources is showing differences. Node1 is different from node2 and node 3.
Can someone help me understand if there is any specific procedure of registering resource extension in clustered environment?
We are using ML 6.0-2.3 version.
Do we need to register resource extension on each node in a cluster? Registering on each node is solving this issue but want to confirm the best approach and how exactly the resource extensions registration works?
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the General