We currently have a Shared Job which does internally do a sequence of steps using the parameters passed. While executing multiple instances of Shared Job, it has been identified that the component is going in Wait/Hang mode, while waiting for one of the Shared Job component to execute. Has anyone encountered this issue before? If yes, how did you solve this?
When using Shared Jobs you will still encounter queuing based on the number of threads available. See the Job Concurrency documentation at https://documentation.matillion.com/docs/en/2969798 "When a job is running, it's given a pool of threads to run its tasks. The number of threads in each pool defaults to 2*n processors. For more information, read our instance sizes guide."
Thanks @AKelly . However, in our case, number of threads isn't an issue. It was informed that we will not be able to run the same transformation job in parallel with different parameters (though the jobs are encompassed in a Shared Job). My understanding was that occurs only when the jobs are run multiple times , however, it happens while the jobs are run in parallel too.
Concurrent Connections Supports Parallelism of Transformation Jobs (matillion.com)