When running jobs that were deployed from artifacts on Nexus or from .zip files they always hand for a really long time on "Requesting run" part before running. We are using TAC 6.3.1 What might be the problem?
All tasks that are deployed from artifacts on nexus or from zip files, stange thing it happens every run not only during the first one. I hangs on requesting run for 20-40 minutes and then thwe actual job execution takes 2 - 10 seconds which is normal
I have been struggling with the same issue for 2 months. We are using talend 6.2.1 Talend Bigdata platform.
When I start a job from jobconductor, the status will be "Requesting to Run" for an hour and then job starts.
This happens when job is running on a different server(execution server) not where TAC is installed. Please adivise?
i have made some testing on both v6.2.1 and v6.3.1, and I can't reproduce the problem, my TAC server and Job server are installed on the same machine. I think there is a network connection delay between TAC server and Job server or TAC server and TAC database server. For testing, install a local Job server on the same machine where TAC is installed, deploy a task to the this local job server and run it to check if the problem exists.
I am facing the same issue.
We are using Talend Data Integration 6.2.1 and when I start a task in a remote jobserver it hangs with status "Requesting to Run"
the log file displays the pipe is broken
WARN AbstractObjectClient - Relais brisÃ© (pipe) java.net.SocketException: Relais brisÃ© (pipe) at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109) at java.net.SocketOutputStream.write(SocketOutputStream.java:153) at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1877)