nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Queuing Deployments

Natasha

Hi All,

We have a 2 tier deployment architecture( Base -> Middle - > Destination)
Base - 6.1.1
Middle - 6.2 SP1(upgraded from 6.1.1)
Destination - 6.2 SP1

We are running a deployment from base which has 3 definitions which is deploying the content on middle tier to a common path and the configuration which runs from middle tier deploys the content from this common path to final server.

Now, this scenario was working fine until 6.2. With the new version in place, it has started throwing the followng error :-
[HTML]
ENG: 2009-06-12 11:27:53 BST GMT+01:00 Thread-275***ERROR - Error encountered while starting deployment LiveSiteEbfRuntime/LiveSite/codeDeployebf
Error: DEPLOYMENT_QUEUED, - There is already a deployment 'codeDeployebf' running. Request to start it now cannot be done. Queuing deployment to run later.
ENG: 2009-06-12 11:27:53 BST GMT+01:00 Thread-275***ERROR - Got null MacroDeploy handle !
Failed to start next multi tier deployment LiveSiteEbfRuntime/LiveSite/codeDeployebf.
[/HTML]

What I understand from this error is all the 3 definitions are trying to call the next deployment( 3instances) which is causing the issue and the first one which starts first gets completed and the other two get failed.

We dont have path registry enabled on any of the servers.

Please help.

Thanks
Natasha.

Find more posts tagged with

Comments

sniv

Hey Natasha,

Do use pathRegistryChecking to enable concurrency management on the receivers side. i.e. on Middle and Destination servers.

Regards,
Vinayak

Natasha

Hey Natasha,

Do use pathRegistryChecking to enable concurrency management on the receivers side. i.e. on Middle and Destination servers.

Regards,
Vinayak

Thanks Vinayak, I will enable this path registry but any idea how was it working in OD 6.1.1 release of middle tier because the problem started coming only when we upgraded OD to 6.2 SP1?

-natasha.

sniv

Hey Natasha,

pathRegistryChecking addresses conflicts/collisions resulting from simultaneous receipt of like-named files deployed into the same target file location.

Situations like :
1) Multi-definition deployments where the definitions share colliding target
directories. (across-parallel-legs)
2) Multi-path definitions where the source-target pairs share colliding target directories (within a leg)
3) Multiple independent deployments that each have a definition with colliding target directories.

PathRegistryChecking prevents these conflicts by allowing only one deployment leg to have access to a particular target directory path sequence at any given time.

Regards!
Vinayak

Adam Stoller

Also, I believe, pathRegistryChecking is only applied for transactional deployments - because of the way that transactional deployments create .iwold and .iwnew directories during the deployment.

There is also a KB article (61497) that documents two other settings which can be used to "tune" the pathRegistryChecking algorithm (or something like that) - they're also covered in the release notes and admin guide for OD 621

Natasha

I tried adding pathRegistryChecking="yes" on odbase.xml(receiver for first deployment), did a server reset and added blockCheckInterval="5" blockMaxWaitTime="300" to the OD configuration file on source side. By looking at the receiver logs, it seems that registry check is not enabled :-
[HTML]
ENG: 2009-06-16 08:54:29 BST GMT+01:00 Thread-1344 Begin logfile [/usr/iw-home/OpenDeployNG/log/LiveSite/rcv.codeDeployEBF.Properties.snv49004
.to.snv24024.log] ---------
ENG: 2009-06-16 08:54:29 BST GMT+01:00 Thread-1344 Job ID=m93 Deployment=LiveSite/codeDeployEBF.Properties.snv24024
ENG: 2009-06-16 08:54:29 BST GMT+01:00 Thread-1344 OpenDeploy Version is 6.2.0.0.0
ENG: 2009-06-16 08:54:29 BST GMT+01:00 Thread-1344 Owner started the deployment is root
ENG: 2009-06-16 08:54:29 BST GMT+01:00 Thread-1344 Internal config file is /usr/iw-home/OpenDeployNG/db/.odrcvr.20014
ENG: 2009-06-16 08:54:29 BST GMT+01:00 Thread-1344 ** Simulate flag = true
ENG: 2009-06-16 08:54:29 BST GMT+01:00 Thread-1344 ** Synchronous flag = true
ENG: 2009-06-16 08:54:29 BST GMT+01:00 Thread-1344 exiting initial
ENG: 2009-06-16 08:54:29 BST GMT+01:00 Thread-1344 entering setup
ENG: 2009-06-16 08:54:29 BST GMT+01:00 Thread-1344 Path registry check (sec): checkinterval=5
ENG: 2009-06-16 08:54:29 BST GMT+01:00 Thread-1344 Path registry check disabled
[/HTML]

Am I missing any step of configuration for enabling it?

sniv

Hey,

Its hard to tell without looking into files. So if possible do upload the Config files where you have done changes.

I.e. Base , Middle ,Destination servers.

Regards!
Vinayak