Anatoly Myachev03/23/2022, 8:20 PM
? There is no logs in Orion UI except
'task-b610b3b0-0' - Crash detected! Execution was interrupted by an unexpected exception.
but it's possible to see it in CloudWatch console. It contains the following error:
RuntimeError: IOLoop is closed
. Note: Orion is deployed on Kubernetes via
Exception: 'RuntimeError("Cannot orchestrate task run \'9987d480-fad1-433a-9749-077a63fbdc0a\'. Failed to connect to API at <http://orion:4200/api/>.")'
, then it makes much more sense to use
? Would you want to give it a try?
Anatoly Myachev03/23/2022, 8:33 PM
. However, I am experimenting with a possible case where there are not enough resources in the current Kubernetes cluster and I want to perform part of the load in AWS cluster (EKS/ECS). So in this case, work will occur with two different clusters.
Current K8s cluster is a k3s running on one AWS host.
. If you're interested, you can follow the dask-task-runner tag or the kube-cluster tag on Discourse to get notified about any tutorials/content/recipes about it
but of course, if you would want to build and contribute one, that would be super appreciated as well!
Anatoly Myachev03/23/2022, 8:51 PM