Hi,

I am currently experiencing an issue where if I have multiple nodes configured in an environment (for arguments sake lets say that it is 2) and then try to add an additional node (in this example a third node) at a future point in time I will see the following error;

2017-06-27 05:34:34,895 [non.c1.macquarie.com] [ STANDARD] [ ] [ ] ( internal.mgmt.PREnvironment) ERROR - com.pega.pegarules.pub.PRRuntimeException: This node not found in the database - Either the record was never saved or was deleted. Unable to join the cluster
2017-06-27 05:34:34,904 [non.c1.macquarie.com] [ STANDARD] [ ] [ ] ( etier.impl.EngineStartup) ERROR - PegaRULES initialization failed. Server: ip-10-160-187-35.syd.non.c1.macquarie.com
com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed

...
Caused by: com.pega.pegarules.pub.PRRuntimeException: This node not found in the database - Either the record was never saved or was deleted. Unable to join the cluster

This is obviously correct as we have never created that instance before but is severely limiting for both auto-scaling practices and CI/CD since we need to use distinct IP addresses which is not feasible in my situation. Is there anything that I can do to turn this feature off or is there a way to register all IP addresses that have access to the database and then remove those that aren't active?

Thanks,

Elliot

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.