From a68c9a7c0772e8cf647998ab5e84f6f54ad5fa13 Mon Sep 17 00:00:00 2001 From: Ana <84312885+AnaLoznianu@users.noreply.github.com> Date: Wed, 25 Oct 2023 18:25:56 +0300 Subject: [PATCH] Update developers/compute-to-data/compute-workflow.md Co-authored-by: Alex Coseru --- developers/compute-to-data/compute-workflow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developers/compute-to-data/compute-workflow.md b/developers/compute-to-data/compute-workflow.md index 78c6b239..e7874b7f 100644 --- a/developers/compute-to-data/compute-workflow.md +++ b/developers/compute-to-data/compute-workflow.md @@ -35,7 +35,7 @@ The consumer selects a preferred environment from the provider's list and initia ## Running the Algorithm on Data Asset(s) 15. The operator engine launches the algorithm pod on the Kubernetes cluster, with volume containing data asset(s) and algorithm mounted. 16. Kubernetes runs the algorithm pod. -17. When the algorithm completes processing the dataset, the operator engine receives confirmation. +17. The Operator engine monitors the algorithm, stopping it if it exceeds the specified time limit based on the chosen environment. 18. Now that the results are available, the operator engine starts "pod-publishing". 19. The pod publishing uploads the results, logs, and admin logs to the output volume. 20. Upon successful upload, the operator engine receives notification from the pod publishing, allowing it to clean up the job volumes.