Multiple instances of OpenDeploy

Hello,

I have setup multiple instances of OpenDeploy (with Datadeploy enabled in both the instances, DAS is disabled in both the instances and standalone deployments are set to yes in both the instances).

I am trying to run datadeployments using the new instance I created (the default one being initial) but the DD deployments do not occur correctly unless the primary/initial OpenDeploy along with the datadeploy module is up & running.

When I submit the request using the clt (by specifying the -inst option), the new OD instance gets the request but then fails to deploy with a error message that it cannot communicate with DataDeploy. I made sure that the datadeploy daemon of the second instance is available by using telnet. The new OD instance is trying to connect to the primary OD's datadeploy module instead of its own. I made all the config changes as specified in the documentation but have not been able to crack this. Any help is appreciated.

Thanks,
Raghavendar

Find more posts tagged with

Comments

traghu

Can someone please help with this issue. Thanks.

Migrateduser

I'll look into this. What's the version of OD? I assume you have set up licensing for DD properly.

Mariam

traghu

OD version is 6.0.2. Yes, I have setup the license properly

Migrateduser

When I submit the request using the clt (by specifying the -inst option), the new OD instance gets the request but then fails to deploy with a error message that it cannot communicate with DataDeploy. I made sure that the datadeploy daemon of the second instance is available by using telnet. The new OD instance is trying to connect to the primary OD's datadeploy module instead of its own. I made all the config changes as specified in the documentation but have not been able to crack this. Any help is appreciated.

You need to use the -odinst option, not the -inst option. The -inst option allows you to run multiple instances of the same job at the same time. The -odinst option tells OD/DD which instance to run the command on. I'm sorry that it is confusing, but the -inst option came long before the -odinst option and we couldn't change the name of the -inst option without breaking things for existing customers.

Thanks,
Mike