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 Open Deploy jobs

Balu110

Today I observed a behavior with Open Deploy 5.6 on Solaris 8

An user executed a Open Deploy job (Say job A using config file A.xml) but for some reason the job was taking some time to complete the deployment to the servers. After about 3-4 mins another user executed another job (say job B using config A) but the user received an error stating Open Deploy Failed. While looking at the logs I found that job A is still in processing and unable to queue job B.

The question is why the Open Deploy is not queuing the deployments? Is there any parameter where I can configure this functionality?

Any help on the greatly appreciated.
-- Balu

Find more posts tagged with

Comments

Migrateduser

There have been other threads on this topic.

You can use the -inst option to run multiple instances of the same deployment config, but only if you don't have colliding files on the target.

The pend session feature can be used to keep the most recently submitted job on the queue. It's really only useful for comparison deployments, not file list.

If you upgrade to OD 6, you can use -inst and configure the receiver to use the concurrency management feature, which queues up deployments on the receiver side that are attempting to update the same target areas.

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

rrose

I am having same problem with my deployments. If two more users are running the same deployment configuration, the second one is rejected from Queue. I want to use the option -inst taskid in my deployments, but my concern is the for each deployment a separat log will be created created by task id, is it good practice. Please advise and also let me know can I implement the -inst without concurrency management and if so what are concequences.

Thanks in advance.

Migrateduser

You can use -inst to run multiple instances with out concurrency if you are not deploy same or conflicting files to the recever server. Below is a scenario that might help you understand the -inst feature and concurrency feature of the receiver server.

OD Receiver with concurrency management
Deployment Instance 1 (d1): /default/main/br/WORKAREA/w1/file1
Deployment Instance 2 (d2): /default/main/br/WORKAREA/w2/file1

Result at the end of both the deployments:

OD Receiver with concurrency management
file1 will be the exact copy of the file in workarea w2 if the order of the deployments invoked are d1 d2.
file1 will be the exact copy of the file in workarea w2 if the order of the deployments invoked are d2 d1.

OD Receiver with-out concurrency management
file1 can be copy from either w1 or w2 workarea if the order of the deployments invoked are d1 d2
file1 can be copy from either w1 or w2 workarea if the order of the deployments invoked are d2 d1
You can tell the which file is deployed if not using concurency management feature on the receiver.

Adam Stoller

...
OD Receiver with concurrency management
Deployment Instance 1 (d1): /default/main/br/WORKAREA/w1/file1
Deployment Instance 2 (d2): /default/main/br/WORKAREA/w2/file1

Result at the end of both the deployments:

OD Receiver with concurrency management
file1 will be the exact copy of the file in workarea w2 if the order of the deployments invoked are d1 d2.
file1 will be the exact copy of the file in workarea w2 if the order of the deployments invoked are d2 d1.
...

In the second case - since d1 was executed after d2 - I believe the resulting file at the other end will be the file in w1 - wouldn't it?

Migrateduser

Yes that was a copy/past error, thanks for correcting Adam.

rrose

Thanks batasari and Fish for your replies. In my case I have only one workarea and each user has a separate folder/files from where/which they will be deploying to a same folder on Target.
Could you please tell me how is it going to effect the logs generation. So will I have a log file for each deployment. Is it good practice.

Thanks very much

Adam Stoller

Thanks batasari and Fish for your replies. In my case I have only one workarea and each user has a separate folder/files from where/which they will be deploying to a same folder on Target.
Could you please tell me how is it going to effect the logs generation. So will I have a log file for each deployment. Is it good practice.

Thanks very much

You will get a different log file for each leg of each instance of a deployment. Having the different log files is not a question of practice, it's a question of product design - and while sometimes it seems a drag, it can also be very nice to have...

rrose

Thanks Fish for your reply. I am going to implement -inst in my deployments to overcome the problem.