cannot use cluster_kwargs timeout because I need to specify an address and I get the error

"Cannot specify `address` and `cluster_class`/`cluster_kwargs`"

other suggestion how to specify the timeout?

reading dask.distributed.Client documentation,

tiemout: Timeout duration for initial connection to the scheduler

I believe the problem is during normal call to the cluster to execute operations, hence I was trying to change the value:

dask.config.set({"distributed.comm.timeouts.connect": 20})

. don't know how to pass this as an argument to client though

Ah, found it, hardcoded in distributed not in the config. Thinking through a solution now, but I know where it's coming from.

Ok, this will require a patch to Prefect (for now), probably will push up a patch to distributed to resolve this for everyone. We usually release on tuesdays, so the fix should hopefully be out the door by EOD today for you to try.

Distributed's config system evolved over time, and not all timeouts are configured by it (currently). The timeout you're seeing is from creating a

Client

on a

Worker

, which is hardcoded in Dask's distributed scheduler as

3s

. This code path is only hit in Prefect if you're using an existing dask cluster (meaning you pass in an

address=

to

DaskExecutor

). If you let the

DaskExecutor

create and manage its own temporary dask cluster this code path won't be hit at all.

I'm going to push a patch to prefect to force this timeout to use the proper distributed config value. You can then adjust this via environment variable or dask config value, rather than using the hardcoded value. The default will also be higher (10s, same as the connect timeout in other places).