This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results forย 
Search instead forย 
Did you mean:ย 

Ensure serial child pipeline execution

kmiesse
Contributor

โ€Ž09-13-2017 12:03 PM

On the Pipeline Execute snap, if I have the Reuse checkbox unchecked and the pool size =1, does that ensure the executions of the child pipelines are serial and not parallel? I want to ensure only one instance of the child pipeline is running at any time and that one execution completes before another begins.

0 Kudos
11 REPLIES 11

tstack
Former Employee

โ€Ž09-13-2017 12:06 PM

Yes, a pool size of 1 means that only one child will be executed at a time and the Pipeline Execute snap will wait for the current child execution to finish before starting the next one.

vyasyash
New Contributor III
In response to tstack

โ€Ž09-13-2017 12:07 PM

But the drawback is you canโ€™t leverage the parameters dynamically in this particular scenario.

0 Kudos

tstack
Former Employee
In response to vyasyash

โ€Ž09-13-2017 12:08 PM

Can you elaborate? The OP mentioned that reuse was off, so the parameters passed to the child pipeline can change for each execution.

vyasyash
New Contributor III
In response to tstack

โ€Ž09-13-2017 12:13 PM

Actually weโ€™ve developed a reusable component - service to reprocess failed transaction and then individual interface pipelines. In case of failures with interface pipelines, we will use the re-processing service to resend the failed transactions. By using pipeline execute in the reprocess service we want to achieve parallel execution on different failed pipelines with each failed transaction calling individual interface pipeline sequentially.

We get parallel execution of each pipeline and sequential processing of documents in the order of input (with reuse option set to 1), but this does not support change in pipeline parameter values. Hence we will have to send the payload, runid and parameters as input documents instead of pipeline parameters.

Weโ€™ve raised a ticket 20085 for this issue. If youโ€™ve a solution for our situation please share will be really helpful.

0 Kudos