[MarkLogic Dev General] Issue with Registering Resoruce extenion in cluster

Gnanaprakash.Bodireddy at cognizant.com Gnanaprakash.Bodireddy at cognizant.com
Thu Mar 12 02:16:36 PDT 2015

HI Josten/Erik

Our cluster configuration is as below

3 Nodes Cluster  with 1 D-Node and 2 e-Nodes

All the content, modules, services are in D-Node.

We are using D-Node also for now as e-Node.

Using our build we are registering our Rest Resource Extensions on Node-1 where our services exists.

Sometime e-Nodes are not showing up the registered resources when I try to see in /v1/config/resources

Using our ELB requests are coming to all of these 3 nodes and only Node 1 is able to serve the request. Rest both e-Nodes are saying resource extension does not exist.

I registered again on both e-Nodes which solved the problem.

Should we forcefully register on all nodes? I believe it's not correct as in cluster all nodes should pick them up automatically.

I want to understand how registration works internally. While registering we use host name (in our case node1), how it works in cluster. Is that something I am missing here?


Message: 3
Date: Thu, 12 Mar 2015 08:14:15 +0000
From: Geert Josten <Geert.Josten at marklogic.com>
Subject: Re: [MarkLogic Dev General] Issue with Registering Resoruce
        extenion in cluster
To: MarkLogic Developer Discussion <general at developer.marklogic.com>
Message-ID: <D1270927.854D6%geert.josten at marklogic.com>
Content-Type: text/plain; charset="us-ascii"

Hi Gnanaprakash,

Some details on the layout of the cluster, regarding group/host/forest arrangements, could be helpful as well..


From: Erik Hennum <Erik.Hennum at marklogic.com<mailto:Erik.Hennum at marklogic.com>>
Reply-To: MarkLogic Developer Discussion <general at developer.marklogic.com<mailto:general at developer.marklogic.com>>
Date: Thursday, March 12, 2015 at 12:35 AM
To: MarkLogic Developer Discussion <general at developer.marklogic.com<mailto:general at developer.marklogic.com>>
Subject: Re: [MarkLogic Dev General] Issue with Registering Resoruce extenion in cluster

Hi, Gnanaprakash:

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?

Erik Hennum

From: general-bounces at developer.marklogic.com<mailto:general-bounces at developer.marklogic.com> [general-bounces at developer.marklogic.com<mailto:general-bounces at developer.marklogic.com>] on behalf of Gnanaprakash.Bodireddy at cognizant.com<mailto:Gnanaprakash.Bodireddy at cognizant.com> [Gnanaprakash.Bodireddy at cognizant.com<mailto:Gnanaprakash.Bodireddy at cognizant.com>]
Sent: Tuesday, March 10, 2015 3:38 AM
To: general at developer.marklogic.com<mailto: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?

Gnanaprakash Bodireddy

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.

More information about the General mailing list