When subworkflows/tasks are not run because the ex...
# ask-the-communityf
Felix Ruess
01/05/2023, 4:54 PMWhen subworkflows/tasks are not run because the exceed the resource quota, shouldn't they automatically start running once enough resources are available again or the limits were increased?
Right now the tasks stay in running, but nothing happens...
y
Yee
01/05/2023, 6:03 PM
yes. they should. do you see that not happening?
Yee
01/05/2023, 6:03 PM
that issue isn’t entirely related right?
Yee
01/05/2023, 6:04 PM
that bug is an admin bug… when it creates the pod, admin isn’t respecting the project/domain level setting, but is creating the pod with the base Admin settings instead
Yee
01/05/2023, 6:05 PM
but once the Pod is created, with whatever resources it’s created with, that behavior should take over
f
Felix Ruess
01/05/2023, 6:06 PMI updated the cluster-resource via flytectl first, that didn't work as per the bug.
I then increased the defaults in the my helm chart values and updated that, which restarted flyteadmin, then they correctly were launched automatically
Felix Ruess
01/05/2023, 6:07 PMDidn't see that at first, because in console it all shows as running, and only in the details you see that the actual status is queued or so
y
Yee
01/05/2023, 6:08 PM
got it, yeah the statuses are a bit misleading
Yee
01/05/2023, 6:08 PM
thanks
f
Felix Ruess
01/05/2023, 6:11 PMAny plans to improve that as well? The correct information seems to be there....
y
Yee
01/05/2023, 6:14 PM
reporting and observability is definitely a topic high on the list in general. mind filing an issue for it though with some screenshots if you see it again?
f
Felix Ruess
01/05/2023, 6:18 PMsure
Felix Ruess
01/05/2023, 6:28 PMNot quite the same as the exceeded resource quota, but the more common queued: https://github.com/flyteorg/flyte/issues/3211
y
Yee
01/05/2023, 8:02 PM
thank you!
152 Views