Closed click2cloud-Nagaraj closed 12 months ago
Hi, @click2cloud-Nagaraj. Thank you for sharing the logs. We have seen an increase in timeouts since last release's migration to async.io. We have improved the stability of the cluster and haven't experienced similar issues internally. The fix will be available on the next release.
Hi, @click2cloud-Nagaraj. Are you still experiencing this issue?
Closing this issue for now. @click2cloud-Nagaraj, feel free to reopen it if the problem persists.
Hello @rafaspadilha, As discussed earlier, now I'm able to extract the orchestrator and worker node logs for the Timeout error and attaching the same here. So, the first time we see the error, might reflect at any point of the workflow run on a particular cluster for a particular workflow. Thereafter, with the same earlier configurations or for any other farm on that particular cluster, Timeout error occurs immediately. Restarting the cluster, works as a temporary workaround though.
Herewith, I'm attaching the following information
Timeout-error-logs.zip
Edit: While running the same workflow we encountered 6 failures before its successful completion. So, I'm attaching log files for all these failures in below given Failures_log_files.zip
Failures_log_files.zip