Execution plan gets triggered even though it's already running

Six Stars

Execution plan gets triggered even though it's already running

I've an execution plan scheduled to run every 15 min, sometimes it takes longer than that and it gets executed again so I end up with two running instances of the same execution plan. 

I would expect it to wait for the other execution to finish or just don't do anything at all. 

Is this the expected behaviour? (multiple executions) is there a way to change it?

 

 

Thanks,

Damian

Moderator

Re: Execution plan gets triggered even though it's already running

Hello,

On execution of the first execution plan, it acquires a lock on that particular task and the second execution plan will wait for the first plan to complete and release the lock.

You can create two different tasks in Job Conductor and assign them to two different execution plans that will trigger to execute at the same time.

Let us know if it is OK with you.

Best regards

Sabrina

--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.

2019 GARNER MAGIC QUADRANT FOR DATA INTEGRATION TOOL

Talend named a Leader.

Get your copy

OPEN STUDIO FOR DATA INTEGRATION

Kickstart your first data integration and ETL projects.

Download now

What’s New for Talend Summer ’19

Watch the recorded webinar!

Watch Now

Self-service Talend Migration: Moving from On-Premises to the Cloud

Move from On-Premises to the Cloud by following the advice of experts

Read Now

Modern Data Engineering in the Cloud

Learn about modern data engineering in the Cloud

Watch Now

How to deploy Talend Jobs as Docker images to Amazon, Azure and Google Cloud reg...

Learn how to deploy Talend Jobs as Docker images to Amazon, Azure and Google Cloud registries

Blog