cancel
Showing results for 
Search instead for 
Did you mean: 

Pipeline STOPPED even though it was not stopped manually and did not time out?

vonkendu
New Contributor II

Hi guys!

So we have a typical parent/child pipeline call (using Pipeline Execute snap). Child pipeline is loading data from one DB to another (a LOT of data). Basically, parent splits data into 10 chunks, then child pipeline is getting called 10 times sequentially to load the data. 

For some reason, parent pipeline becomes STOPPED after about 50 minutes of execution. STOPPED, not errored out. The only error I can see in the logs is: daemon prio=4 Id=444 TIMED_WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@4930dd68

Can someone please assist? 

 

Thank you!

0 REPLIES 0