Daan
Get list of avavailable workers not running jobs
Some context: use case: we want to only enable certain actions in the app (using the "disabled" fields) when a background runnable returns a certain result. In this case, we can't "trigger" this background runnable from the app, it should basically "poll" for available workers in the background.
How should we most elegantly do this? Is there a "windmill way" of only enabling certain actions if workers are actually available or is the approach: they will be put in a queue always. Can we for example make a flow "fail" if no worker is available & then not queue them?
8 replies
Get list of avavailable workers not running jobs
We see this for example
"worker_group": "large_8192mb",
"wm_version": "v1.437.1-2-g343cd02ad",
"occupancy_rate": 0.35248488,
"occupancy_rate_15s": 0.0,
"occupancy_rate_5m": 0.0,
"occupancy_rate_30m": 0.040873528,
What does occupancy rate represent here? The total since the worker was launched?
8 replies
Question on scaling strategy in Docker
Hi Ruben - OK, clear; Our question is not so much about having less than 1GB for a worker, but more about flexibly being able to use the full capacity for whichever job is available on the server to start next.
But I understand that we are responsible for deciding upfront which memory constraints are assigned to which worker pool, & which jobs are assigned to which worker. This is the part that is now causing issues (aka some flows use most of the time a very small footprint, but can sometimes take up more memory - we would like not having to reserve this capacity in a "large worker" pool)
7 replies
Bug? Attached runnable to button but shows empty in UI (for 1 specific table & button)
Hah - cleared all caches, logged out & into Windmill again - removed the component entirely & recreated it, and it works again. So I think I just wasted a few of your minutes, sorry for that - I can't reproduce it anymore
8 replies
Bug? Attached runnable to button but shows empty in UI (for 1 specific table & button)
I don't really know - but visually, it shows on the right the inputs to the runnable script (so it's somehow fetching those correctly - in this case "path") , but when I come back to the component a second later, the view shows again at the top to "select a script" (while the path variable is still there).
8 replies
Bug? Attached runnable to button but shows empty in UI (for 1 specific table & button)
Sorry - not sure how to sure more details, figured you might link this to a known issue. Can provide more details, I'm trying a bunch of things like clearing caching in browser etc now too.
8 replies