https://prefect.io logo
Title
t

Tsang Yong

11/12/2019, 12:26 AM
hey, I’m getting these in the logs. is this something I in my workflow code or dask config or prefect?
dask-worker[65048]: distributed.core - INFO - Event loop was unresponsive in Worker for 3.21s.  This is often caused by long-running GIL-holding functions or moving large chunks of data. This can cause timeouts and instability.
j

Jeremiah

11/12/2019, 12:27 AM
Hi @Tsang Yong - that’s a Dask log which you’ll usually see if your task has seized the CPU entirely (so no background processes can run) — are you doing something particularly intensive?
(Another way you can see this is if you’re running a dask worker / scheduler on something like a laptop and you sleep the computer; when you turn it back on it’ll show this message)
t

Tsang Yong

11/12/2019, 12:29 AM
yes it’s a CPU intensive task
j

Jeremiah

11/12/2019, 12:30 AM
Ok, that could be normal — just Dask warning you that it wasn’t able to run any background task while your task was running.
j

josh

11/13/2019, 6:43 PM
@Marvin archive “distributed: Event loop was unresponsive in Worker”