We are Using Parallel Chunk Loop(use automatically chunk count) to call workflows by using “Call workflow (table based)” .
Table Creator(6 Rows) -> Parallel Chunk Start-> Call workflow (table based) -> Parallel Chunk End
※ CPU has a 4-core processor, 8 logical processors by the result of msinfo32 command
This workflow worked well for months, but today it crashes with an error: ERROR Call Workflow (Table Based) 0:18: Execute failed: Read timed out
How to solve the problem? Do I need to increase time-out value?
Thanks in advance.
Thank you very much for your quick response.
Yes, We are calling a local workflow,
But the Java version is 1.8.0_152 , and OS is Windows Server 2016 in our environment,
It seems the error has nothing to do with the issue.
The workflow worked well in this morning, but failed in the afternoon.
KNIME Sever : 4.82
KNIME ANALYTICS PLATFORM: 3.72
Thank you for that information. Would you mind also sharing your KNIME log? Do you use the KNIME AP locally and as the server’s executor? I am wondering if the actual invokation of the workflow fails or if the workflow itself fails because some node throws the error. Can you trigger the workflow you are trying to call manually, e.g. from the AP and find out which node it is that gives you problems?
I got the log but unfortunately it does not give away more than the error message. You raise good questions. If the workflows are mounted on a network drive, this could cause performance issues. @laughsmile could you give us some more info on the setup?
I think you would have to take a step back and think about how to construct your workflow and at which point to call parallel workflows. Maybe you could provide us with an example or a screenshot about what the workflow does.
If the thing continues to be unstable you might have to think about ‘communicating’ with the workflow(s) and make them to report back when they finished successfully and maybe have a Variable Condition Loop End at the end, and maybe also some Error catcher.
One more question: how did you configure the node? It has options for short and long running workflows. Did you specify that the workflow runs long? See here for more info: https://kni.me/n/M66aoaj-gqFbGR5j