Queuing a Deployment when it is already Running

Hey All,

We have a fairly simple deployment model which syncs via checksum comparison whatever is in STAGING with the Web Server. It's simple and has been working quite well.

As we have more users submitting content for deployment, it happens from time to time that they will attempt to start the deployment while it is already running (same Deployment definition), and as a result the second requested deployment fails with the below message:

Start deployment xyz/xyzContentDeployment. iwodstart running in default synchronous mode. Need to wait for deployment to complete. ***ERROR - Starting deployment. Reason from server: DEPLOYMENT_NOT_QUEUED Details : Deployment xyzContentDeployment is already running. Request to start it now cannot be done. Rejecting request.

It is a transactional deployment, and in an effort to have the second deployment queued, we've tried adding the following to odbase to enable Time Based Serialization. Unfortunately it seems that this only serializes which webservers to send to, and does not enable the queuing of subsequent requested deployments.

[html]

[/html]

Any other thoughts on how we might queue the second request for deployment (and yes I understand that the second deployment may/will be redundant given it's nature). Understandably our users are nervous when they see OpenDeploy Errors in their workflow.

Find more posts tagged with

Comments

nipper

How are you initiating OD ? IIRC, you can use the -inst flag and use the same parameter, which should queue them. I know I have gotten that to work before, just cannot recall exact steps.

jasonmcneil

Thanks Nipper

We're using the Out of the box Deploy Task with the WFM. I'll play around a bit and try setting the inst to the jobId and let you know the results!

jasonmcneil

As an update, this does allow multiple deployments to happen simultaneously, thus suppressing the message, I'm just a bit nervous about two area compare deployments taking place at the same time (as opposed to queuing them back to back).

nipper

You can set the base server to run sequential or concurrent deployments. If you put the base in sequential mode, then you have to use -inst with a unique ID to get it to go concurrently (other than the ones you are working on)

The OD Admin manual talks about it.

Adam Stoller

For concurrent transactional deployments targeting the same target area (not necessarily the exact same path within the target area) you want to look at several things:

Search the manuals, the DTDs, and/or KB articles for more information regarding these items.