Adding an Reload node

[jpjust]

Hi All,

I have an question and I hope some one can shed some details.

So I have an Dev and Prod clustered environment. 1 Dev node and 2 prod node. The 2 prod node acts as Engine, repository, proxy and scheduler nodes.  Out of that 1 node acts as master and slave which is central node.

Now, I am  getting an additional node and wanted to classify as ONLY scheduler slave node and remove the existing 1 node from scheduler (slave)

How can I go about adding an scheduler node to existing cluster and removing an existing node from scheduler (slave)?

What role this existing scheduler node will play when I remove scheduler service (I will have Repository, Engine and proxy running), will it just act as consumer node only?

Thanks

[rohitk1609]

If I try to understand your site architecture:

There are three servers in your site: 2 which are for  production use(Central server whose scheduler is set to  1 node acts as master and slave) and 1 for development.

If your central server is master and slave it means reloads happen on central server too. 

When you say"I am  getting an additional node and wanted to classify as ONLY scheduler slave node and remove the existing 1 node from scheduler (slave)"

Clasify as Only scheduler slave node and remove existing 1 node from schedule server so where exactly the difference is if you want to remove  1 node from scheduler (slave) and add new node which is classify as ONLY scheduler slave node?

If you add a node for reloads only then it has to be slave, isn't it?

About this "What role this existing scheduler node will play when I remove scheduler service (I will have Repository, Engine and proxy running), will it just act as consumer node only?"

When you say existing scheduler node, are you talking about central server?

[jpjust]

Thank you Rohit for the comments.

So I have 3 nodes as below.

Dev Node - Run repository, engine, proxy - only for dev purpose

Prod node (Central node) - Run all services - Engine, repository, proxy and scheduler nodes - This is classified as master and slave

Prod node (RIM Node)- Run all services - Engine, repository, proxy and scheduler nodes - This is classified as slave

Now we have resource consumption and looking to add an scheduler ONLY node. So what services I have to enable in this new node only to run reloads?

Do you think if this is an good idea having central node with all services, another RIM node with all services and another RIM node only with scheduler? DO you think if there is any node that I can classify as consumer ONLY?

Please let me know your suggestions. 

Thanks

[Maria_Halley]

@jpjust

There are some deployment examples in the help that would be worth looking at, if you haven't already.

Deployment Examples